Methods for the interconnection of fibre channel over ethernet devices using shortest path bridging

ABSTRACT

Methods are provided for forwarding Fiber Channel over Ethernet (FCoE) frames over a TRILL network by a FCoE device interconnection apparatus (FIA). A FCoE frame is received from a FCoE device at the FIA. The frame includes at least destination Ethernet MAC address and source Ethernet MAC address fields. The destination Ethernet MAC address of the incoming frame is replaced with the MAC address of the remote FCoE device as determined by the Fiber Channel destination address identifier in the received frame. The source Ethernet MAC address of the incoming frame is replaced. The frame is encapsulated in a TRILL header. The frame is forwarded to an egress FCoE device interconnection apparatus (FIA). The frame is then decapsulated into a FCoE frame, which is forwarded to an attached FCoE device with the original destination and source Ethernet MAC addresses.

RELATED APPLICATION INFORMATION

This patent application is related in subject matter to United Statespatent application entitled “Methods, Systems and Apparatus for theInterconnection of Fibre Channel Over Ethernet Devices”, filed Jan. 7,2011 (U.S. Ser. No. 12/987,057, now U.S. Pat. No. 8,625,597); UnitedStates Patent Application entitled “Methods, Systems and Apparatus forthe Interconnection of Fibre Channel Over Ethernet Devices Using a FibreChannel Over Ethernet Interconnection Apparatus Controller”, filed onJan. 7, 2011 ( U.S Ser. No. 12/987,063), now U.S. Publication No,2012/0177042; United States patent application entitled “Methods,Systems, and Apparatus for the Servicing of Fibre Channel Fabric LoginFrames”, filed on Jan. 7, 2011 (U.S. Ser. No. 12/987,066, now U.S. Pat.No. 8,559,433); United States patent application entitled “Methods,Systems and Apparatus for Utilizing an iSNS Server in a Network of FibreChannel Over Ethernet Devices”, filed on Jan. 7, 2011 (U.S. Ser. No.12/987,073, now U.S. Publication No 2012-0177370); United States patentapplication entitled “Methods. Systems and Apparatus for theInterconnection of Fibre Channel Over Ethernet Devices Using a TRILLNetwork”, filed on Jan. 7, 2011 (U.S. Ser. No. 12/987,077, now U.S.Publication No 2012-01770415); and United States patent applicationentitled “Methods, Systems and Apparatus for Converged NetworkAdapters”, filed on Jan. 7, 2011 (U.S. Ser. No. 12/987,076, now U.S.Pat. No. 8,559335; which are all incorporated herein by reference as iffully set forth herein.

FIELD OF THE INVENTION

The disclosures and embodiments of the invention relate to networksystems and communications networks, more particularly, certainembodiments of the invention relate to a method and system for FibreChannel over Ethernet networking, Fibre Channel networking, and IEEE802.2 frame forwarding.

BACKGROUND OF THE INVENTION

Today they are at least two separate networks found in Data Centers. Themore ubiquitous of the networks, the Local Area Network (LAN), is basedon the Ethernet protocol and is mainly used for server to server andserver to Internet communications. The other network, the Storage AreaNetwork (SAN), is specialized to carry server to storage communications.The Data Center SAN is mainly based on the Fibre Channel protocol andhas the following characteristics: low latency, high bandwidth, and aloss-less network. Recently there have been innovations to merge the SANwith the LAN. The promised benefits include a savings from the reducedequipment needs and the resulting savings on the amount of equipmentreal estate, power, and cooling required. Newly created standardscomprising this LAN/SAN convergence define how SAN frames, namely FibreChannel protocol frames, are mapped over the Ethernet network. These newframes are called Fibre Channel over Ethernet (FCoE) frames. Additionalstandards define how to make the Ethernet network lossless, i.e., to addflow control at the network level to prevent Ethernet frames from beingdropped due to congestion. Still other standards define how to segmentthe transmission line into classes that virtually separate thecommunications over the transmission line.

Converging the LAN and SAN networks has created additional complexity inthe management, control, and data switching areas. Singly, the FibreChannel switch fabric protocols are very complex and have shown to benot very interoperable between the small number of vendors who buildproducts that support them. Mapping the Fibre Channel switch fabricprotocols over Ethernet has resulted in a dizzying amount of newstandards that have inhibited the market acceptance of the Fibre Channelover Ethernet (FCoE) mapping over this new converged network. Newswitches have been defined called Fibre Channel Forwarders (FCFs) andFibre Channel Data Forwarders (FDFs), which add Fibre Channel overEthernet and Ethernet elements to the already complex Fibre Channelswitch architecture. FCFs and FDFs interconnect ENodes, which are FibreChannel or devices nodes that are able to transmit Fibre Channel overEthernet frames. There have been some standards and innovations appliedto ENodes, and their embedded Virtual N_Ports (VN_Ports), to connectwithout using FCFs or FDFs. One of these efforts defines an ENode toENode connection method, called VN_Port to VN_Port (VN2VN) wherebyENodes can connect to each other over a Lossless Ethernet networkwithout an FCF or FDF. Other methods have been suggested to move some ofthe FCF/FDF intelligence to the ENode. Both the emerging VN2VN standardand the emerging direct ENode direct connect methods have manysignificant disadvantages. These disadvantages include but are notlimited to: the requirement for the ENode to choose a unique MediaAccess Control (MAC) address for each VN_Port, the requirement for theENode to choose a unique Fibre Channel address identifier for eachVN_Port, the lack of visibility into the network's supported maximumframe size or other capabilities, the lack of standardized discovery ofspecific ENode types such as Storage targets, the lack of the ability toautomatically and dynamically create Fibre Channel zones or accesscontrol lists (ACLs) for intermediate Ethernet bridges, the lack ofvisibility to load balance across several paths from a source ENode to adestination ENode based on FCIDs, and the increased complexity to scaleto hundreds of ENodes which requires error prone manual configuration.Due to the lack of Fibre Channel fabric control, these emerging ideasand standards target smaller networks of ENodes, which are impracticalin today's Data Center.

In parallel with the innovations around converging the LAN and SAN,there have also been a trend to virtualize servers, i.e., consolidate acorporation's many underutilized servers onto fewer more utilizedservers. The server virtualization trend has many advantages, includingmore utilization of existing underutilized servers, lower equipmentspace, power, and cooling requirements since there are fewer servers.This trend results in fewer and higher utilized servers which havechanged the traffic characteristics of the LAN that interconnects them.The traffic requirements which used to be flowing from Internet toServer have changed to an any-to-any server flow. This migration intraffic patterns has produced a trend to “flatten” LANs, i.e.,consolidate the normally three layers (core, distribution, and access)of switches commonly found in a Data Center to two layers (core andaccess). In parallel with this physical flattening trend is the trendtowards utilizing layer 2 forwarding methods to keep the network in asingle broadcast domain, which helps support any-to-any connectionrequirements of virtualized servers and their hypervisors. New linklevel protocols have been defined to accelerate the ability for any toany server based virtual machine communications. Many of these new linklevel protocols need new switch hardware and new ways to manage theresulting network.

What is needed is a simpler way to converge the LAN and SAN in ascalable and less complex method than the trajectory of both thestandards committees and emerging ENode to ENode inventions. What isalso needed is have this simpler method be more compatible with thetrend towards flattening the large Data Center networks. Both simplermethods need to be easily managed, scalable, and interoperable.Accomplishing this would accelerate the LAN/SAN network convergencetrend and accelerate the flattening of the LAN to more easily attain thebenefits of virtualization, convergence, and consolidation.

BRIEF SUMMARY OF THE INVENTION

Methods, apparatus and systems are provided for forwarding Fibre Channelover Ethernet (FCoE) frames over a Shortest Path Bridged network with aFCoE device interconnection apparatus (FIA). A FCoE frame is receivedfrom a FCoE device, the frame including at least destination EthernetMAC address and source Ethernet MAC address fields. The destinationEthernet MAC address of the incoming frame is replaced with the MACaddress of the remote FCoE device as determined by the Fibre Channeldestination address identifier in the received FCoE frame. The sourceEthernet MAC address of the incoming frame is replaced. The frame isencapsulated in a MAC header. The frame is forwarded to an egress FCoEdevice interconnection apparatus (FIA). Thereafter, the outer MAC headerof the received frame is decapsulated into a FCoE frame. Thedecapsulated frame is forwarded to an attached FCoE device with theoriginal destination and source Ethernet MAC addresses

Methods, apparatus and systems are provided for forwarding Fibre ChannelInitialization Protocol (FIP) frames and Fibre Channel over Ethernet(FCoE) frames by a FCoE device interconnection apparatus (FIA) and witha Fibre Channel over Ethernet device interconnection apparatuscontroller (FIAC). In one aspect, a FIP frame is received from a FCoEdevice by a FIA. The FIP frame includes at least a destination andsource Ethernet Media Access Control (MAC) address fields. The receivedFIP frame is forwarded to a FCoE device interconnection apparatuscontroller (FIAC) over an Ethernet link. The FCoE frame received by theFIA from the FCoE device includes at least destination and sourceEthernet MAC address fields. The destination and source Ethernet MACaddresses are replaced, such as where the destination Ethernet MACaddress is replaced by the MAC address assigned to a remote FCoE device,such as the desired end port. Finally, the frame is forwarded to thedestination FCoE device. Preferably, first and second ports are coupledto the connectivity apparatus, which are then coupled to first andsecond FCoE devices.

Methods, apparatus and systems are provided for forwarding Fibre ChannelInitialization Protocol (FIP) and Fibre Channel over Ethernet (FCoE)frames by a FCoE device interconnection apparatus (FIA) and a FibreChannel over Ethernet device interconnection apparatus controller(FIAC). In one aspect of the invention, a command is sent from a FIAC tothe FIA to set the frame processing apparatus to identify received FIPframes, which are forwarded with the original destination and sourceEthernet Media Access Control (MAC) addresses. A FIP frame received bythe FIA is identified and forwarded by the frame processing apparatus. Acommand is sent from the FIAC to the FIA to identify received FCoEframes, and to have the source and destination Ethernet MAC addresses insaid received FCoE frame replaced. When a FCoE frame is received by theFIA, the source and destination Ethernet MAC addresses are replaced,such as where the destination Ethernet MAC address of the receivedmatched FCoE frame is replaced by the MAC address assigned to thedesired end port. The FCoE frame is forwarded to a destination FCoEdevice.

Methods, apparatus and systems are provided for processing Fibre ChannelFabric Login frames by a FCoE device interconnection apparatus (FIA) anda FCoE device interconnection apparatus controller (FIAC). A FabricLogin (FLOGI) Fibre Channel frame is received from a Fibre Channeldevice at a Fibre Channel device interconnection apparatus (FIA). TheFLOGI Fibre Channel frame is encapsulated into a Fibre Channel overEthernet (FCoE) FIP FLOGI frame at the FIA. The encapsulated frame istransmitted from the FIA to a FCoE device interconnection apparatuscontroller (FIAC). At the FIAC, the FIP FLOGI frame is received andprocessed. Thereafter, a FIP link service accept (LS_ACC) frame istransmitted by the FIAC to the FIA, and the FIP LS_ACC frame is receivedby the FIA. The FIP frame is decapsulated into a Fibre Channel LS_ACCframe at the FIA. The Fibre Channel LS_ACC frame is transmitted back tothe said Fibre Channel device. Preferably, first and second ports arecoupled to the connectivity apparatus and adapted to receive FCoE andFIP frames, which are then coupled to first and second FCoE devices.

Methods, apparatus and systems are provided for assigning Fibre ChannelDomain identifiers with an iSNS Server, a Fibre Channel over Ethernetdevice interconnection apparatus controller (FIAC), and a Fibre Channelover Ethernet device interconnection apparatus (FIA). A Request DomainIdentifier iSNS protocol message is sent from a FCoE deviceinterconnection apparatus controller (FIAC) to a iSNS Server. A RequestDomain Identifier iSNS protocol message reply is received from the iSNSServer by the FIAC. A Fibre Channel Initialization Protocol (FIP) FabricLogin (FLOGI) frame is received from a Fibre Channel over Ethernet(FCoE) device by a FCoE device interconnection apparatus (FIA). The FIPFLOGI frame is forwarded by the FIA. At the FIAC, a new Fibre Channeladdress identifier is assigned, using the Domain Identifier assignedfrom the Request Domain Identifier response message. At the FIAC, a FIPlink service accept (LS_ACC) response is transmitted to the FIP FLOGIcomprising the newly assigned Fibre Channel address identifier at theFIAC. At the FIA, the FIP LS_ACC is received and forwards the FIP LS_ACCframe to the FCoE device that transmitted the FIP FLOGI frame.

Methods, apparatus and systems are provided for forwarding Fibre Channelover Ethernet (FCoE) frames over a TRILL network by a FCoE deviceinterconnection apparatus (FIA). A FCoE frame is received from a FCoEdevice at the FIA. The frame includes at least destination Ethernet MACaddress and source Ethernet MAC address fields. The destination EthernetMAC address of the incoming frame is replaced with the MAC address ofthe remote FCoE device as determined by the Fibre Channel destinationaddress identifier in the received FCoE frame. The source Ethernet MACaddress of the incoming frame is replaced. The frame is encapsulated ina TRILL header. The frame is forwarded to an egress FCoE deviceinterconnection apparatus (FIA). The frame is then decapsulated into aFCoE frame, which is forwarded to an attached FCoE device with theoriginal destination and source Ethernet MAC addresses.

Methods, apparatus and systems are provided for creating virtual linksbetween Fibre Channel over Ethernet (FCoE) nodes. FIP DiscoveryAdvertisement frames are received from multiple FCoE deviceinterconnection apparatus (FIA). The FIP Discovery Advertisement framespreferably includes source Ethernet MAC addresses, a destinationEthernet MAC address of All-ENode-MACs, Fabric FIP descriptor, and aPriority FIP descriptor. A list is stored of one or more of the sourceEthernet MAC address, FIP Priority descriptor, and FIP Fabric descriptorfor each unique FIP Discovery Advertisement frame received as indicatedby the Fabric descriptor. The Name Server is queried for each sourceEthernet MAC address in said storage. For all FCoE devices that match inmore that one Name Server, connect to those FCoE devices using thehighest priority Ethernet MAC address from matching list items.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings illustrate only exemplary embodiments of the invention andtherefore do not limit its scope because the inventive concepts lendthemselves to other equally effective embodiments.

FIG. 1 illustrates the prior art FC-BB_E mapping of Fibre Channel levelsand sublevels over IEEE 802.3 layers.

FIG. 2 shows the prior art FC-BB_E definition of end devices, an ENodeand a FCoE Forwarder (FCF).

FIG. 3 is a diagram showing the prior art FCoE frame format.

FIG. 4 illustrates the prior art FIP frame PDU format.

FIG. 5 is a diagram illustrating the prior art ENode and FCF connectionmodel.

FIG. 6 is a diagram of a prior art FCF functional model.

FIG. 7 is a diagram of a prior art ENode functional model.

FIG. 8 is a diagram of a FIA and FIAC Functional Model.

FIG. 9 is a diagram of a FIA.

FIG. 10 is a detailed diagram of a bridge adapted to implement a FIAwith FCoE frame connectivity.

FIG. 11 is a detailed diagram of an FIA adapted to connect to FibreChannel links and devices.

FIG. 12 is a diagram showing a network of FIA Controllers and FIAs.

FIG. 13 is a diagram showing a FIA Controller controlling a number ofFIAs.

FIG. 14 is a diagram of a Converged Network Adapter.

FIG. 15 is a diagram showing the FIA Switch Client in more detail.

FIG. 16 is a diagram showing the FIA Controller in more detail.

FIG. 17 is a diagram showing a policy applied to two FCoE devices.

FIG. 18 is a diagram showing the Discovery Domain model.

FIG. 19 is a diagram showing the FIA connection model.

FIG. 20 is a diagram showing the interconnection of two ENodes through anetwork of FIAs.

FIG. 21 is a diagram showing the interconnection of two Fibre Channeldevices through a network of FIAs.

FIG. 22 is a ladder or sequence diagram showing a FIA Controller settingFrame Matching Entries (FMEs) in a FIA.

FIG. 23 is a ladder or sequence diagram of the FIP Discovery frameexchange protocol between a FIA Controller and a FIA.

FIG. 24 is a ladder or sequence diagram showing a FIP FLOGI Request, FIPFLOGI LS_ACC frame exchange.

FIG. 25 is a ladder or sequence diagram showing the exchange of a FIPNPIV FDISC/FIP LS_ACC message exchange between an ENode and a FIAController.

FIG. 26 is a ladder or sequence diagram showing the exchange of a FCoEState Change Registration request and LS_ACC response message exchangein addition to a Name Server query request and response messageexchange.

FIG. 27 is a ladder or sequence diagram showing a PLOGI exchange betweenENodes.

FIG. 28 is a ladder or sequence diagram showing an ENode and a VN_Porttransmitting a FIP Keep Alive frames.

FIG. 29 is a sequence or ladder diagram showing the initialization of aFIA utilizing an iSNS Server for State Change Notification, DiscoveryDomain, and Name Services.

FIG. 30 is a ladder or sequence diagram showing the interaction betweenan ENode, a FIA Controller, an iSNS Server, and a remote ENode upon theexchange of FLOG/LS_ACC FCoE frames.

FIG. 31 is a ladder or sequence diagram showing the initialization anddiscovery between two ENodes using the FIA Controller and iSNS Server.

FIG. 32 is a ladder or sequence diagram showing the interconnection oftwo native Fibre Channel devices through FIAs with ports adapted toconnect to Fibre Channel devices.

FIG. 33 is a ladder or sequence diagram showing the communicationbetween a ENode and a Fibre Channel Device through FIAs.

FIG. 34 is a diagram showing multiple virtual connections betweenENodes, FIA, and FCFs.

FIG. 35 is a ladder or sequence diagram showing the FIP Discoveryprotocol exchange between an ENode, a FIA Controller, and a FCF.

FIG. 36 is a diagram showing an ENode determining the path to a remotedevice.

FIG. 37 is a diagram showing the generation of FMEs upon the receipt ofa FIP FLOGI or FIP NPIV FDISC frame.

FIG. 38 is a diagram showing the removal of FMEs upon the receipt of aFIP FLOGO frame.

FIG. 39 is a prior art network diagram showing the interconnection ofRouter Bridges (RBridges).

FIG. 40 is a diagram showing the prior art frame format for an Ethernetand PPP encapsulated Transparent Interconnection of Lots of Links(TRILL) frame.

FIG. 41 shows a representative prior art RBridge Port Model in moredetail.

FIG. 42 is a diagram of a TRILL RBridge with the addition of FIA Processand FIA Switch Client capability.

FIG. 43 is a diagram showing the interconnection of ENodes over a TRILLEthernet network.

FIG. 44 is a diagram showing the interconnection of Fibre Channel nodesover a TRILL Ethernet Network.

FIG. 45 is a diagram showing the interconnection of ENodes over aShortest Path Bridging MAC-in-MAC (SPBM) Network.

FIG. 46 is a diagram showing a source and destination Ethernet MACaddress replacement logic.

FIG. 47 is a diagram showing the migration of a Virtual Machine from aserver connected to a FIA to another server connected to another FIA.

FIG. 48 is a diagram showing a distributed FIAC deployment.

ACRONYMS

ACE Access Control Entry

ACL Access Control List

ACLE Access Control List Entry

BPDU Bridge PDU

CNA Converged Network Adapter

DA Destination Address

DCB Data Center Bridging

DCBX DCB Exchange protocol

EISS Extended Internal Sublayer Service

ENode FCoE Node

ETS Enhanced Transmission Selection (IEEE 802.1Qaz)

FC-MAP FCoE Mapped Address Prefix

FCF FCoE Forwarder

FIA FCoE device and Fibre Channel node interconnection Apparatus

FCF-MAC FCoE Forwarder Media Access Control

FCID Fibre Channel address or port identifier

FCoE Fibre Channel over Ethernet

FCoE Device Another term for ENode

FCoE_LEP FCoE Link Endpoint

FDF FCoE Data Forwarder

Fibre Channel device Another term for Fibre Channel node

FIP FCoE Initialization Protocol

FME Frame Match Entry

FPMA Fabric Provided MAC Address

IEEE Institute of Electrical and Electronics Engineers

IP Internet Protocol

IS-IS Intermediate System to Intermediate System

ISS Internal Sublayer Service

LAN Local Area Network

MAC Media Access Control

PDU Protocol Data Unit

PHY Physical Layer

PPP Point-to-Point Protocol

PFC Priority-based Flow Control (IEEE 802.1Qbb, 802.3bd)

RBridge Routing Bridge

SA Source Address

SNMP Simple Network Management Protocol

SPBM Shortest Path Bridging MAC-in-MAC

SPBV Shortest Path Bridging VLAN

SPF Shortest Path First

SPMA Server Provided MAC Address

TRILL Transparent Interconnection of Lots of Links

VE_Port Virtual E_Port

VF_Port Virtual F_Port

VID VLAN Identifier

VLAN Virtual Local Area Network

VN_Port Virtual N_Port

VRP VLAN Registration Protocol

vSwitch Virtual Switch

Constants

-   -   FIP_TYPE: 8914h The value specified in the Ethernet TYPE field        for a FIP PDU    -   FCoE_TYPE: 8906h The value specified in the Ethernet TYPE field        for an FCoE PDU    -   All-FCoE-MACs: 01-10-18-01-00-00 The group address for all FCoE        devices.    -   All-ENode-MACs: 01-10-18-01-00-01 The group address for all        ENodes    -   DEFAULT_FC-MAP: 0EFC00h The default value for the FC-MAP field        in a FIP FC-MAP descriptor        Definitions

Access control lists (ACL): are comprised of Access Control Entries(ACE), allow network managers to define classification actions and rulesfor specific ports. Frames entering the port, with an a ctive ACL, areeither admitted or denied entry.

Address or Port identifier: An address value used to identify source(S_ID) or destination (D_ID) of a frame.

Converged Network Adapter (CNA): is a technology that supports datanetworking (TCP/IP) and storage networking (Fibre Channel) traffic on asingle I/O adapter. CNAs support both Enhanced Ethernet and FibreChannel over Ethernet (FCoE).

Discovery Domains (DD): are a security and management mechanism used toadminister access and connectivity to devices.

Discovery Domain Set (DDS): is a container object for Discovery Domains(DDs). DDSs may contain one or more DDs. Similarly, each DD can be amember of one or more DDSs. DDSs are a mechanism to store coordinatedsets of DD mappings.

Domain Identifier: Bits 23 through 16 of an address identifier.

E_Port: A Fabric “Expansion” Port that attaches to anotherInterconnect_Port to create an Inter-Switch Link. An E_Port is thecombination of one PE_Port and one VE_Port operating together

Encapsulated FC frame: An SOF/EOF delimited FC frame prefixed with a28-byte FC frame Encapsulation Header (see RFC 3643).

ENode: An FCoE Node, a Fiber Channel node (see FC-FS-3) that is able totransmit FCoE frames using one or more ENode MACs. The term ENode andFCoE device is used interchangeably.

ENode MAC: A Lossless Ethernet MAC coupled with an FCoE Controller in anENode.

ENode MAC address: The MAC address used by the FCoE Controller on anENode MAC for the FCoE Initialization Protocol (FIP).

Fabric: As defined in FC-FS-3 an entity that interconnects variousNx_Ports attached to it, and is capable of routing frames using only theD_ID information in an FC-2 frame header.

Fabric_Name: the Fabric_Name (see FC-FS-3) identifying the Fabric.

Fabric Provided MAC Address (FPMA): A MAC address that is assigned by anFCF to a single ENode MAC, and is not assigned to any other MAC withinthe same Ethernet VLAN. A Fabric Provided MAC Address is associated witha single VN_Port at that ENode MAC.

FC-BB_E: a protocol mapping defined in order to transport Fibre Channelover a Lossless Ethernet network.

FCF (FCoE Forwarder): A Fibre Channel Switching Element (see FC-SW-5)that is able to forward FCoE frames across one or more FCF-MACs, andthat optionally includes one or more Lossless Ethernet bridging elementsand/or a Fibre Channel Fabric interface.

FCF-MAC: A Lossless Ethernet MAC coupled with an FCoE Controller in anFCF. In the context of the invention, FCF-MAC also refers to a LosslessEthernet MAC coupled to a modified FCoE Controller in a FCoE deviceinterconnection apparatus controller (FIAC).

FCF-MAC address: The MAC address of an FCF-MAC.

FC-MAP (Mapped Address Prefix): In a Fabric Provided MAC Address, therequired value for the upper 24 bits of a MAC address assigned to aVN_Port.

FCoE Controller: A functional entity, coupled with a Lossless EthernetMAC, instantiating and de-instantiating VE_Ports, VF_Ports, VN_Ports,and/or FCoE_LEPs.

FCoE Device: a term used interchangeable with an ENode

FCoE Device Interconnection Apparatus (FIA): an apparatus thatinterconnects one or more of the following: ENodes, Fibre Channel nodes,FCF, and FDF's. A FIA is capable of substituting source and destinationEthernet addresses and capable of inspecting the Fibre Channeldestination address identifier in received FCoE frames. A FIA is alsocapable of communicating with one or more FIACs. The FCoE DeviceInterconnection Apparatus (FIA) is a term used interchangeably withENode and Fibre Channel node interconnection apparatus and FCoE Deviceand Fibre Channel node interconnection apparatus.

FCoE Device Interconnection Apparatus Controller (FIAC): An ENode andFibre Channel interconnection apparatus controller. The FIAC includes amodified FCoE Controller and a FCF-MAC. The modified FCoE controller iscapable of receiving and processing certain FIP and FCoE frames fromENodes and Fibre Channel Nodes and capable of transmitting certain FIPand FCoE frames to ENodes and Fibre Channel Nodes. The FIAC communicateswith FIA's and optionally other FIACs.

FCoE Entity: The interface, containing one or more FCoE_LEPs, between aVN_Port, a VF_Port, or a VE_Port, and a Lossless Ethernet MAC.

FCoE frame: An Ethernet frame (see IEEE 802.3-2008) that contains anFCoE PDU

FCoE_LEP (FCoE Link End-Point): The data forwarding component of an FCoEEntity that handles FC frame encapsulation/decapsulation, andtransmission/reception of encapsulated frames through a single VirtualLink.

FCoE PDU: A PDU identified by the FCoE Ethernet Type that encapsulates abyte-encoded FC frame.

FDF (FCoE Data Forwarder): a Fibre Channel Switching Element (seeFC-SW-5) that is able to forward FCoE frames across on or more FCF-MACs,and that optionally includes one or more Lossless Ethernet bridgingelements, A FDF includes a subset of FCF features, most notably routingand zoning. A FDF is controlled by a FCF.

FIP frame: An Ethernet frame (see IEEE 802.3-2008) containing a FCoEInitialization Protocol (FIP) PDU.

FIP PDU: A PDU identified by the FIP Ethernet Type that encapsulates oneor more FIP operations

FLOGI: Fabric Login ELS (see FC-LS-2).

Frame Match Entry (FME): A FME is send from a FIAC Controller to a FIA.The FME consists of match fields, counters, and actions. The matchfields are applied against an incoming frame. The match fields consistof the ingress port and frame headers. The actions include instructionson how to handle the incoming frame and the counters are statisticstables.

F_Port: A port by which non-loop N_Ports are attached to a Fabric. Doesnot include FL_Ports (see FC-SW-5 and FC-FS-3).

F_Port_Name: A Name_Identifier that identifies an F_Port Inter-SwitchLink (ISL): A Link directly connecting the E_Port of one Switch to theE_Port of another Switch.

Lossless Ethernet bridging element: An Ethernet bridging functionoperating across Lossless Ethernet MACs.

Lossless Ethernet MAC: A full duplex Ethernet MAC implementingextensions to avoid Ethernet frame loss due to congestion (e.g., thePAUSE mechanism (see IEEE 802.3-2008) or the Priority-based Flow Controlmechanism (see IEEE 802.1Qbb).

LS_ACC: Link Service Accept (see FC-LS-2).

Lossless Ethernet network: An Ethernet network composed only of fullduplex links, Lossless Ethernet MACs, and Lossless Ethernet bridgingelements.

LS_RJT: Link Service Reject (see FC-LS-2).

Name_Identifier: is used to identify entities in Fibre Channel such as aVN_Port, N_Port, node, VF_Port, F_Port, Fabric or other Fibre Channelobjects. The Name_Identifier for an entity shall be unique within theFibre Channel interaction space.

Multicast MAC address: A MAC address associated with a group oflogically related Ethernet stations on an Ethernet network and called aMulticast-Group Address in IEEE 802.3-2008.

PE_Port (Physical F_Port): The LCF within the Fabric that attaches toanother PE_Port through a native FC link (see FC-SW-5).

PF_Port (Physical F_Port): The LCF within the Fabric that attaches to aPN_Port through a native FC link (see FC-SW-5).

PN_Port (Physical N_Port): An LCF that supports only VN_Ports (seeFC-FS-3)

Name_Identifier: A value with a specified size and format used toidentify a Fibre Channel Entity.

Node_Name: A Name_Identifier associated with a node (see FC-FS-3).

N_Port: A device port that generates/terminates FC-4 channel traffic.

N_Port_Name: A Name_Identifier that identifies an N_Port.

Path selection: Path Selection is the process by which a Switchdetermines the best path from a source domain to a destination domain.These paths may then be used in any appropriate manner by the Switch tomove frames to their destinations. This path selection process does notrequire nor preclude the use of static or dynamic load-balancing. Thestandard defines the Fabric Shortest Path First (FSPF) protocol.

PLOGI: N_Port Login (see FC-LS-2).

Router: a device that performs forwarding of IP (L3) packets, based onL3 addressing and forwarding information. Routers forward packets fromone L2 broadcast domain to another (one, or more in the IP multicastcase)—distinct—L2 broadcast domain(s). A router terminates an L2broadcast domain.

Server Provided MAC Address (SPMA): A MAC address that is assigned by anENode to a single one of its ENode MACs, and is not assigned to anyother MAC within the same Ethernet VLAN, A Server Provided MAC Addressmay be associated with more than one VN_Port at that ENode MAC.

Switch_Name: A Name_Identifier that identifies a Switch or a Bridgedevice. The format of the name is specified in FC-FS-3. Each Switch andBridge device shall provide a unique Switch_Name within the Fabric.

Unicast MAC address: A MAC address associated with a particular Ethernetstation on an Ethernet network and called an Individual Address in IEEE802.3-2008.

Virtual Switch: is a software program that allows one virtual machine(VM) to communicate with another virtual machine (VM). A virtual machinecan intelligently direct communication on the network by inspectingpackets before passing them on.

VF_ID: the VF_ID (see FC-FS-3) associated with a Fabric.

VF_Port (Virtual F_Port): An instance of the FC-2V sublevel of FibreChannel that communicates with one or more VN_Ports (see FC-SW-5) andthat is dynamically instantiated on successful completion of a FIP FLOGIExchange.

VF_Port/FCoE_LEP pair: A VF_Port and one of its associated FCoE_LEPs.

VF_Port/FCoE_LEP pair: A VN_Port and its associated FCoE_LEP.

Virtual Link: The logical link connecting two FCoE_LEPs.

VN_Port (Virtual N_Port): An instance of the FC-2V sublevel of FibreChannel that operates as an N_Port (see FC-FS-3) and is dynamicallyinstantiated on successful completion of a FIP FLOGI or FIP NPIV FDISCExchange.

VN_Port MAC address: The MAC address used by an ENode for a particularVN_Port.

Zone: A group of Zone Members. Members of a Zone are made aware of eachother, but not made aware of Zone Members outside the Zone.

Zone Definition: The parameters that define a Zone.

Zone Member: The specification of a device to be included in a Zone.

DETAILED DESCRIPTION OF THE INVENTION

FIGS. 1 through 7 and 39 through 41 describe prior art designs, theunderstanding of which are useful to understand the inventions disclosedand claimed herein. The FC-BB_E model defines the structured operationby which Fibre Channel frames are transported over a Lossless Ethernetnetwork. FC-BB_E protocol mapping is referred to as Fibre Channel overEthernet (FCoE). FIG. 1 illustrates the FC-BB_E mapping 8 of FibreChannel levels and sublevels over IEEE 802.3 layers 9. Fibre ChannelFC-2 1 sublevels, FC-2M 3 and FC-2P 4, are mapped into the FCoE Entity 6which is defined by the FC_BB_E mapping 8. Higher Fibre Channel levels 7remain unchanged. FIG. 2 shows FC-BB_E definition of end devices, anENode 17 and a FCoE Forwarder (FCF) 10. ENodes 17 are Fibre Channelnodes (see FC-FS-3) that are able to transport Fibre Channel overLossless Ethernet 19. FCFs 10 are Fibre Channel Switching Elements (seeFC-SW-5) that are able to transport Fibre Channel over Lossless Ethernet13.

FIG. 3 is a diagram showing the FCoE frame format. FCoE is encapsulatedover Ethernet with the use of a dedicated Ethertype 0x8906 referred inFIG. 3 as FCoE_TYPE 28. The Ethernet header includes a source 26 anddestination 25 MAC address (6 bytes each) and an optional IEEE 802.1QVirtual LAN (VLAN) tag 27. A single 4-bit field (version 29) satisfiesthe IEEE sub-type requirements. The SOF (start of frame) 34 and EOF (endof frame) 36 are encoded as specified in RFC 3643. Reserved bits 30 3132 33 37 are present to guarantee that the FCoE frame meets the minimumlength requirement of Ethernet. Inside the encapsulated Fibre Channelframe 35, the frame header is retained so as to allow connecting to astorage network by passing on the Fibre Channel frame directly afterde-encapsulation. An Ethernet trailer 38 consists of a Frame CheckSequence (FCS). This is where the Cyclic Redundancy Check (CRC) value isheld that will be used to confirm that the frame has not been corruptedwhen it reaches its destination.

The FCoE Initialization Protocol (FIP) is used to perform the functionsof FC-BB_E device discovery, initialization, and maintenance. A newEthernet TYPE frame is specified, different from the FCoE Ethernet TYPEto enable the distinction of discovery, initialization, and maintenancetraffic from other FCoE traffic. FIG. 4 illustrates the FIP frame PDUformat 50 51 52, which consists of the FIP_TYPE 53 Ethernet TYPE,Version 54, and the rest of the encapsulated frame 56.

FIG. 5 is a diagram illustrating the ENode and FCF connection model. Themodel illustrates FCoE VN Port to VP' Port 88 89, VE Port to VE Port 97,VE Port 94 to E_Port 102, and FCF F_Port 101 to N_port 108 virtuallinks. Physical links numbered 84 87 91 and 92 are Ethernet links,physical links numbered 103 and 107 are Fibre Channel links, The VE Portto VE Port virtual connection 97 is an instance of the FC-2V sublevel,see FIG. 6 118 of Fibre Channel that operates as an E Port in accordancewith FC-SW-5 (T11 Fibre Channel Switch) and is dynamically instantiatedtogether with its FCoE_LEP, see FIG. 6 119 on successful completion of aFIP ELP Exchange. Inter-Switch Links (ISLs) 97 are used by FCFs totransmit and receive frames with other FCFs or switches or Bridgedevices. An ISL always connects exactly one E_Port or VE_Port on aSwitch to exactly one E_Port or VE_Port on another Switch or exactly oneB_Port on a Bridge device. ENode H1 81 and ENode H2 85 have a singlephysical Ethernet connection 84 87 to the Lossless Ethernet network 90,while Fibre Channel Device 1 105 has a single physical Fibre Channelconnection 107 to the FCF F_Port 101 in FCF B 98. FCF A 93 and FCF. B 98also have single physical Ethernet connections 91 92 to the LosslessEthernet network 90. Each ENode 81 85 may instantiate multiple VN_Ports80 82 83. As illustrated, the FCF inherits much of the functions andcomplexity of a Fibre Channel switch (i.e., from FC-SW and FC-GS) FCF. A93 VEPort 96 to FCF B 98 VEPort 99 interswitch Link (ISL) 97 and FCFEPort 94 to Switch Fabric 104 EPort 109 Interswitch link (ISL) 109 arestill preserved. VE_Port operation specifies the tools and methods forinterconnection and initialization of FCFs 93 98 to create amulti-Switch Fabric. FCF VE Port operation defines how ports discoverand self-configure for their appropriate operating mode. Once a portestablishes connection to another FCF and/or Fibre Channel Switch and isoperating as a VE Port 94 96 99, an address assignment algorithm isexecuted to allocate port addresses throughout the Fabric and the FSPFFibre Channel based routing algorithm is executed.

FIG. 6 is a diagram of a FCF functional model. The bracketed functioncomponents 134 137, the Lossless Ethernet Bridging Element 125, and theFC Fabric interface 110 are optional. An FCF 136 is functionallycomposed of a Fibre Channel (FC) Switching Element 115 (see FC-SW-5)with at least one Lossless Ethernet MAC 123 (FCF-MAC address). The FCSwitching Element 115 is composed of the following: Path Selector,Router, Switch Construct, Address Manager, and the Fabric Controller.The Router is a logical entity that performs the routing of Class F,Class 2, and Class 3 frames to their final destination. The PathSelector is a logical entity that establishes frame routing paths. PathSelection is the process by which a Switch determines the best path froma source domain to a destination domain using all or part of FibreChannel address identifiers. The FC-SW-5 standard defines the FabricShortest Path First (FSPF) protocol for Path Selection. Each FCF-MAC 123is coupled with an FCoE Controller 122 function. Each FCF-MAC may beoptionally coupled with a Fibre Channel Fabric interface 110, providingnative E_Port 111 112 or F_Port 113 114 connectivity. An FCF 136forwards FCoE frames addressed to one of its FCF-MACs based on the D_IDof the encapsulated FC frames. When an FCF includes Lossless Ethernetbridging elements 125, an FCF-MAC address may be used by multipleEthernet ports 126 128 of the FCF. The FCoE Controller 122 associatedwith an FCF-MAC shall support the instantiation of VE_Port/FCoE_LEPpairs 117 119 or VF_Port/FCoE_LEP pairs 129 131. An FCF-MAC supportingthe instantiation of VF_Port/FCoE_LEP pairs is referred to as a VF_Port129 capable FCF-MAC. A VE_Port 117 receives FC frames from the FCSwitching Element 115 and sends them to its FCoE_LEP 119 forencapsulation and transmission over the Lossless Ethernet network. In asimilar way, a VE_Port 117 sends FC frames received from its FCoE_LEP119 to the FC Switching element 115. A VE_Port 117 is uniquelyidentified by an E_Port_Name Name_Identifier and is addressed by theFabric Controller address identifier (i.e., FFFFFDh). The VE_Port 117behavior is specified in FC-SW-5, with the exception that a VE_Port isinstantiated on successful completion of a FIP ELP Exchange, ignoringthe buffer-to-buffer flow control parameters, rather than on completionof a native ELP Exchange. Similarly, a VF_Port 129 is an instance of theFC-2V 130 sublevel of Fibre Channel that operates as an F_Port inaccordance with FC-SW-5 and is dynamically instantiated together withits FCoE_LEP 131 on successful completion of a FIP FLOGI Exchange, AVF_Port 129 receives FC frames from the FC Switching Element 115 andsends them to the proper FCoE_LEP 131 for encapsulation and transmissionover the Lossless Ethernet network. In a similar way, a VF_Port sends FCframes received from one of its FCoE_LEPs 131 to the Fibre ChannelSwitching element 115. A VF_Port 129 is uniquely identified by anF_Port_Name Name_Identifier and is addressed by the F_Port Controlleraddress identifier (i.e., FFFFFEh). The VF_Port behavior is be specifiedin FC-LS-2 and FC-LS-3, with the exception that a VF_Port isinstantiated on successful completion of a FIP FLOGI Exchange, ignoringthe buffer-to-buffer flow control parameters, rather than on completionof a native FLOGI Exchange.

The FC/FCoE Data Forwarder (FDF) is in the process of being defined bythe T11 standards committee. The FDF is fully controlled by acontrolling FCF and operates according to the information that FCFssends to FDFs. The controlling FCF assigns addresses, computes theroutes, and distributes addresses and routes to its FDFs. A FDF does notneed to compute routes. FDFs instantiate VF_Ports and VA_Ports, VA_Portsbeing the FCF to FDF or FDF to FCF links. FDFs have a similararchitecture to FCFs, VF_Ports and VE_Ports interconnected by a FibreChannel switching element 115.

FIG. 7 is a diagram of an ENode functional model 200. An ENode isfunctionally composed of at least one Lossless Ethernet MAC 215 (i.e.,the ENode MAC), and an FCoE Controller function for each Enode MAC 214.The FCoE Controller 214 associated with an ENode MAC 215 supports theinstantiation of VN_Port/FCoE_LEP pairs 204 206 210 212. The FCoEController 214 is the functional entity that performs the FCoEInitialization Protocol (FIP) and instantiates or de-instantiatesVN_Port/FCoE_LEP 204 206 210 212 pairs as needed. The FCoE_LEP 206 212is the functional entity performing the encapsulation of FC frames intoFCoE frames in transmission and the decapsulation of FCoE frames into FCframes in reception. When encapsulating FC frames into FCoE frames, theMAC address of the local link end-point is used as source address andthe MAC address of the remote link end-point is used as destinationaddress of the generated FCoE frame. For an FCoE_LEP 206 212 of an ENodeMAC, the MAC address of the local link end-point is the MAC addressassociated with its VN_Port and the remote link end-point address is theFCF-MAC address associated with the remote VF_Port. A VN_Port receivesFC frames from the upper FC levels and sends them to its FCoE_LEP 206212 for encapsulation and transmission over the Lossless Ethernetnetwork. In a similar way, a VN_Port sends FC frames received from itsFCoE_LEP to the upper FC levels. A VN_Port is uniquely identified by anN_Port_Name Name_Identifier and is addressed by the address identifierthe Fabric assigned to it.

FIG. 8 is a diagram of a FCoE Device and Fibre Channel NodeInterconnection Apparatus (FIA) and Controller (FIAC) Functional Model.The model shows a FIAC 251 comprising a modified FCoE Controller 253coupled to a Lossless Ethernet MAC 254 which contains at least oneEthernet Port 255 coupled to an Ethernet link 257. The RAC Ethernet_Port255 contains a FCF-MAC. Other FIAC Modules 252 are represented by asingle box. The other FIAC Modules 252 are described in FIG. 16. TheOther FIAC Modules 252 may be coupled to the Lossless Ethernet MAC 254and the modified FCoE Controller 253. There can be one or more FCoEdevice and Fibre Channel Node Interconnection Apparatus (FIA) 264 in anetwork all under the control of a single FIAC 251. The FIA 264 includesa plurality of Port logic 266 267 268 269 coupled to a Frame ForwardingSwitch 265 and a Frame Processing Apparatus 285. The Frame ForwardingSwitch is capable of forwarding frames between ports 266 267 268 269 byusing several methods comprising one or more of the following: STP,RSTP, MSTP, TRILL, Shortest Path Bridging, MPLS, VPLS, OSPF, RIP, andBGP. The Frame Processing Apparatus 285 includes but is not limited toone more 278 Frame Match entries (FME) 270 271, one or more 298 accesscontrol list entries (ACLE) 290 291, and one or more 287 Policy entries284 286. Both FMEs and optionally ACLEs are sent from the FIAC 251 tothe FIA 264 upon instantiation and de-instantiation of VN_Ports andN_Ports. Policy entries 284 are sent to the FIAs 264 by the FIAC 251 atany time as they are typically configured asynchronously with VN_Portand N_Port instantiation. Policy entries configure the flow meteringcapability in the Frame Processing Apparatus 285 to assign differentflow quality of services to a specified VN_Port pair, N_Port pair, orVN_Port to N_Port pair. Each ACLE 290 291 preferably includes an ingressport, source and destination Ethernet MAC address fields, a EthernetTYPE field, a action which permits the frame to be forwarded or deny,which discards the frame, and optionally a Fibre Channel addressidentifier field. When multiple ACLEs 290 291 describe the same incomingframe, the Frame Processing Apparatus 285 matches the first ACLE in it'sAccess Control List. Each FME 270 271 preferably includes an ingressport, a priority, frame match fields, counters, and actions. If two FMEsmatch an incoming frame, the highest priority FMEs actions are executed.The frame match fields are applied to incoming frames and comprise theingress port, frame headers, and select encapsulated frame fields suchas the Fibre Channel Destination Address Identifier (DID) field. Theframe match fields can match exactly or utilize wild cards to maskcertain subfields of the incoming frame. FME counters are updated formatched frames. FME counters may comprise the following: transmitted andreceived frames and bytes, transmitted and receive errors, and frametype transmitted and received. FME actions are instructions to performupon frame matches comprising but not be limited to: forward the frame,flood the frame, replace certain frame fields or subfields, add certainframe fields, subfields, or headers such as the MAC header (MAC-in-MAC),a VLAN header (QinQ), and tag frames, the tags comprising a MPLS headerand a VPLS header. The Ethernet_Ports contained in the Port Logic areconnected to Ethernet Links 275 276. The FCF-MACs 272 contained in theFIA Port logic 266 267 268 269 in addition to the FCF-MACs contained inother FIAs and FIACs 256 may contain the same FCF-MAC address value. TheFIA Port Logic 262 may be adapted to connect to a Fibre Channel node orfabric 263. A Fibre Channel adapted FIA Port Logic 262 includes FibreChannel FC0 and FC1 layer support 261, a FCoE_LEP 259, a connection tothe frame forwarding switch 258, and a connection to the FrameProcessing Apparatus 285. The FCoE_LEP 259 encapsulates Fibre Channelframes received from the Fibre Channel link 263 and decapsulates FCoEand FIP frames received from the Frame Forwarding switch 258. ReceivedFLOGI, NPIV FDISC, and LOGO frames are encapsulated 259 into FIP framesby the FIA with the destination Ethernet MAC address equal to theFCF_MAC address of the FIAC. A MAC address, a FME, and optionally a ACLEare assigned to each N_Port by the FIAC to identify that N_Port withinthe Lossless Ethernet network. The FIAC 251 receives and processes theFIP FLOGI, FIP NPIV FDISC, and FIP LOGO frames encapsulated by a FIAFibre Channel adapted port 262 and responds with FIP responses. The FIPresponses are decapsulated 259 by the FIA Fibre Channel adapted port 262into Fibre Channel frames and transmitted out the link 263. The modifiedFCoE Controller 253 in a FIAC 251 sends commands to all FIAs, thecommands comprising add, delete, or modify FMEs, get and clear counters,and add, delete, or modify ACLEs. The modified FCoE Controller 253contained in the FIAC 251 preferably includes, but is not limited to,the following capabilities: (1) participates in the FIP VLAN discoveryprotocol initiated by an ENode MAC, (2) participates in the FIPdiscovery protocol initiated by an ENode MAC, (3) sends add FME commandsand add ACLE commands to FIAs upon successful completion of each FIPFLOGI Exchange initiated by an ENode MAC, (4) sends add FME commands andadd ACLE commands to on successful completion of each FLOGI initiated bya Fibre Channel Node, (5) sends add FME commands and add ACLE commandsto FIAs on successful completion of each FIP NPIV FDISC Exchangeinitiated by an already logged in ENode MAC, (6) sends add FME commandsand add ACLE commands on successful completion of each NPIV FDISCExchange initiated by an already logged in Fibre Channel Node, (7) whena VN_Port is logged out, sends a delete FME command, the FME associatedwith that VN_Port and a delete ACLE command, the ACLE associated withthat VN_Port, (8) when a N_Port is logged out, sends a delete FMEcommand, the FME associated with that VN_Port and sends a delete ACLEcommand, the ACLE associated with that VN_Port, (9) initiates FIP ClearVirtual Link request as needed to terminate Virtual Links to VN_Ports,(10) monitors that status of the instantiated VN_Ports and N_Ports, (11)transmits periodic FIP Discovery Advertisements to the All-ENode-MACsaddress every FKA_ADV_PERIOD, (12) monitors that status of the logged inENode MACs by verifying that periodic FIP Keep Alive frames are receivedwithin FKA_ADV_PERIOD, unless the D bit is set to one in receivedDiscovery Advertisements, and (13) monitors that status of the logged inVN_Ports by maintaining timers and verifying that periodic FIP KeepAlive frames are received within FKA_VN_PERIOD, unless the D bit is setto one in received Discovery Advertisements. In addition to FMEs forVN_Ports and N_Ports, the RAC sends add FME commands to all FIAscomprising the following: to match FIP frames with the destinationEthernet MAC address of All-ENode-MACs, All-FCF-MACs, and FCF-MAC of theFIAC, to match FIP frames with a source Ethernet MAC address of theFCF-MAC of the FIAC, to match FCoE frames with a source Ethernet MACaddress of the FCF-MAC of the FIAC, and to match FCoE frames with adestination Ethernet MAC address of the FCF-MAC of the FIAC. In additionto ACLEs for VN_Ports and N_Ports, the FIAC may send add ACLE commandsto all FIAs comprising the following: to match and permit FIP frameswith the destination Ethernet MAC address of All-ENode-MACs,All-FCF-MACs, and FCF-MAC of the FIAC, to match and permit FIP frameswith a source Ethernet MAC address of the FCF-MAC of the FIAC, to andpermit FCoE frames with a source Ethernet MAC address of the FCF-MAC ofthe FIAC, and to match and permit FCoE frames with a destinationEthernet MAC address of the FCF-MAC of the FIAC. Frames with the wellknown Fabric services addresses in the Fibre Channel destination addressidentifier are forwarded to the FIAC 251 for processing. FMEs 270 271may replace source and destination Ethernet MAC addresses in receivedFCoE frames when identifying and matching the embedded Fibre Channeldestination address identifier (DID).

As will be appreciated by those skilled in the art, the functionalityand structures of the inventions may be functionally and physically asdescribed herein, or may be arranged and organized into multiplecomponents or sub-components, and may be grouped differently into a moreconsolidated or more distributed grouping or groupings. For example, theprocesses may be implemented in software, firmware or hardware, or anycombination thereof. By way of further example, the functionality orstructure may be implemented in software and reside in a physicalserver, in a virtual machine in a virtual server, in a communicationswitch, or in a storage array. Each component may comprise one or morephysical components. The components may be located at a singlegeographic location or may be distributed geographically. Theflexibility in the nature of the invention applies to all of theinventions described and claimed, herein.

FIG. 9 is a diagram of a FIA 300. The FIA may include but is not limitedto one or more 315 Receive (Rx) Port Logic 314 316, one or more 319Transmit (Tx) Port Logic 318 320, a Switch Apparatus 317, a FrameProcessing Apparatus 306, Core Logic 304, an Embedded Processor 301,Memory 302, and several Peripherals 303 305. The Transmit and ReceivePort Logic 314 316 318 320 may include but is not limited to thefollowing frames, mappers, and or MACs: Ethernet, Lossless Ethernet,Fibre Channel, SONET/SDH, ATM, and Wave Division Multiplexing. TheSwitch Apparatus allows frames to be transferred between the Rx PortLogic 314 316 and the Tx Port Logic 318 320. The Frame ProcessingApparatus 306 may inspect and operate on frame headers and body, and mayforward frames to the Core Logic 304. Frames forwarded to the Core Logic304 may be stored in the memory 302 and may be operated on by theEmbedded Processor 301. The ingress 307 apparatus may contain framematching rules and actions that are applied to received frames. Theframe matching rules may match fields from the incoming framescomprising but not be limited to: the source and destination EthernetMAC addresses, the VLAN identifier, the VLAN priority, the IP sourceaddress, the IP destination address, the IP protocol, the TCP/UDP sourceand destination ports, the Fibre Channel source and destination addressidentifier, the Fibre Channel OXID/RXID, R_CTL, and TYPE fields. Theframe actions may include replacing or substituting the source EthernetMAC address, replacing or substituting the destination Ethernet MACaddress, adding or removing a MAC header (MAC-in-MAC), adding orremoving a VLAN field (QinQ), and adding or removing a TRILL header. Anexample Ethernet MAC address replacement apparatus is illustrated inFIG. 46. The frame matching rules may be configured by a FIAC. The FrameFiltering 308 apparatus may forward frames based on but not limited tothe following frame fields: VLAN identifier, VLAN priority, destinationEthernet MAC address, and source Ethernet MAC address. The FrameFiltering 308 apparatus may implement a number of frame forwardingmethods including but not limited to Rapid Spanning Tree Protocol(RSTP), Spanning Tree Protocol (STP), Multiple Spanning Tree Protocol(MSTP), Per-VLAN Spanning Tree (PVST), Rapid Per-VLAN Spanning Tree(R-PVST), Shortest Path Bridging (SPB), TRILL, Open Short Path First(OSPF), and Border Gateway Protocol (BGP). The Ingress 307 apparatus mayact in parallel and independent from the Frame Filtering 308 apparatus.For example, an incoming frame is modified by the ingress 307 apparatusand “forwarded” to the Frame Filtering 308 apparatus which applies aforwarding method based on the modified frame. The example illustratesthe independent actions of the frame modification with frame forwarding.The Flow Metering 310 apparatus may apply flow classification andmetering to frames received. Flow classification identifies a subset oftraffic (frames) that may be subject to the same treatment in terms ofmetering and forwarding. Flow classification rules may be based on butnot limited to the destination MAC address, the VID, and the frame class(see Priority Flow Control IEEE 802.1Qbb). The Queuing Frame 311apparatus manages the transmission of frames and may implement PriorityFlow Control (PFC), Enhanced Transmission Selection (ETS), and otherpriority frame transmission methods. Together the modules 307 308 309310 311 comprising the Frame Processing Apparatus 306 allow fine-grainedcontrol of frame forwarding, which can support QoS, tunneling, andfilter rules. Further, the Embedded Processor 301 is capable configuringthe Frame Processing Apparatus 306, setting the fine-grain framematching and field replacement modification actions. The EmbeddedProcessor is also adapted to communicate with a FIAC to receive commandscomprising but not limited to add, delete, modify FME and ACLEs, get andclear counters, heartbeat, and configure flow metering. The FME andACLEs may be implemented in the Ingress apparatus 307. Some of the FMEactions may also be implemented in the Frame Filtering apparatus 308,such as tunneling and tagging actions associated with forwarding methodssuch as Shortest Path Bridging (SPB). Many variations can be applied toFIG. 9 without changing the functions including distributing the FrameProcessing Apparatus 306 over several ports and or physical chassis,adding additional Embedded processors 301 and core logic 304, and addingmore functions to the Frame Processing Apparatus 306.

FIG. 10 is a detailed diagram of a bridge adapted to implement a FIA.Each port 420 421 coupled to an ENode may contain a FIA Process 444 407.The FIA Process 444 407 delivers and accepts frames to and from theBridge Port Transmit and Receive Process 445 408, MAC Relay Entity orForwarding Process 402 and LLC Entities 442 413 that may include but arenot limited to Higher Layer Entities such as the FIA Switch Client 416,Rapid Spanning Tree Protocol Entity 415 (and/or other layer 2 forwardingmethods), Bridge Management Entity, Generic Attribute RegistrationProtocol (GARP) Entity. The Rapid Spanning Tree Protocol Higher LayerEntity 415 is connected to all port LLCs 442 413 including connection tothe Port State 400 405, the Filtering Database 403, and the FIA 444 407processes. The FIA Switch Client 416 is also connected to each Port LLC442 413 and can exchange information and frames with the FIA Process 444407. The FIA Switch Client 416 manages communications from the FIA to aFIA Controller. The Filtering Database 403 supports the addition,modification, and deletion of static filtering information by the FIASwitch Client 416. Although the adapted bridge in FIG. 10 is shown withonly two ports 420 421, a plurality of ports can be defined.

FIG. 11 is a detailed diagram of an FIA adapted to connect to FibreChannel links and Fibre Channel devices. The apparatus of FIG. 11 isadapted 453 465 454 455 467 468 to communicate with Fibre Channel links456 469, The FIA Process 453 465 is also modified to couple with theFibre Channel Links 456 469. The FIA FC Process 453 465 receives andtransmits frames from and to the FC 1 blocks 454 467, MAC Relay orForwarding Process 459 and LLC Entities 452 464 that may support HigherLayer Entities which may include but not be limited to: an FIA SwitchClient 471, a Rapid Spanning Tree Protocol Entity 451, a BridgeManagement Entity, a Generic Attribute Registration Protocol (CIARP)Entity. The Rapid Spanning Tree Protocol Higher Layer Entity 451 isconnected to all port LLCs 452 464 which may include but not be limitedto connection to the Port State 457 463 and Filtering Database 461processes. The FIA Switch Client 471 is also connected to each Port LLC452 464 and can exchange infbrmation and frames with the FIA FC Process453 465.

FIG. 12 is a diagram showing a network of HA Controllers and FIAs. Thediagram shows a primary FIA Controller 500 and a backup FIA Controller501. The FIA Controllers access FIA 1 503 and FIA 2 504 over acommunications network 502, which may comprise but not be limited to anEthernet network, a SONET network, a TRILL network, a Shortest PathBridging network. The FIA Controller 500 501 can be located anywhere inthe network and be coupled to the network over multiple paths. The FIAincludes a FIA Switch Client 505 507 and Switching Hardware 506 508. TheFIA Controller 509 sends and receives commands to the FIA Switch Client511. The FIA Controller 509 commands may be send using but not limitedto the following protocols: SNMP, Command Line Protocol (CLP), OpenFlow,and proprietary protocols 510. The FIA Controller 500 and FIA ControllerBackup 501 may utilize a virtual FCF-MAC address. The virtual FCF-MACaddress would be assigned to the FIA Controller 500 until the FIAController 500 fails. The FIA Controller Backup 501 would then claim theFCF-MAC address, receive frames destined to the FCT-MAC address, andtransmit frames using the FCF-MAC address as the source Ethernet MACaddress. FIA Controller failure may be detected by the exchange of aheartbeat message between the FIA Controllers. If the heartbeat messageis not received within predetermined parameters such as time andretries, then the FIA Controller backup would assume communicationsusing the virtual FCF-MAC address. Further, the FIA Controller and theFIA Controller backup may synchronize it's data structures, i.e., listof instantiated VN_Ports and N_Ports comprising their WWN's, MACaddresses, and Fibre Channel address identifiers.

FIG. 13 is a diagram showing a FIA Controller 567 controlling 565 566569 a number of FIAs 555 558 570. FIA capabilities can be embedded inHypervisor virtual switches 555 to control the virtual software switch575 embedded in the virtual switch. FIA capabilities can be embedded inConverged Network Adapters 558, controlling the embedded switch 560which switches frames between PCIe bus queues 557, between the PCIe busqueues 557 and the Ethernet links 561 562, and between the Ethernetlinks 561 562. FIA capabilities in a CNA 558 control 580 the embeddedswitch by adding, modifying, and removing switch entries upon commandsfrom the FIA Controller 567. FIA capabilities can also be embedded inEthernet Switches or Bridges 570, controlling the switching hardware orfabric 572. To embed FIA capabilities, a small FIA Switch Client, FIG.14, is embedded in the target apparatus 556 559 571. The FIA SwitchClient may configure the local device Frame Processing Apparatus orequivalent apparatus under the control of the FIA Controller 567. TheFIA Controller 567 can control 565 566 569 the switching apparatus inthe targeted apparatus 560 575 572 either through a direct connection orthrough a communications network 564.

FIG. 14 is a diagram of a Converged Network Adapter (CNA). FIG. 14 issimplified for clarity purposes. The CNA 592 interfaces with a server orstorage subsystem over a PCIe interface 581. The PCIe Interfacetransmits both data and control frames to the CNA 592. The CNA 592 maycomprise a Embedded bridge or switch 582 to forward frames between butnot limited to the following: Ethernet Ports 589, PCIe functions orqueues 581, FIA Switch Client 583, FCoE_LEP 584, Fabric Services FrameHandler 585, FCF-List Storage 586, PLOGI Frame Handler 587, NameServices and the Query Handler 588. Note that one or more of theaforementioned blocks 583 584 585 586 587 588 may be located in softwareexternal to the CNA 592. The FCoE_LEP 584 encapsulates andde-encapsulates Fibre Channel frames to either FIP or FCoE frames. TheFabric Services Frame Hander 585 processes frames from the fabric to theCNA 592. The FCF-list storage includes at least FCF-MAC addresses, VIDs,Priority attributes, and Fabric attributes. The PLOGI frame handler 587may transmit PLOGI frames to Fabric Servers, VF_Ports, F_Ports,VN_Ports, and N_Ports. The Name Services Query Handler 588 signals thePLOGI Frame Handler 587 to send PLOGI frames.

FIG. 15 is a diagram showing the FIA Switch Client in more detail. TheFIA Switch Client 600 is designed to interface with a host switch FIG.13 555 558 570 utilizing a number of methods. Each FIA Switch Client 600can utilize one or more concurrent methods. The FIA Switch Client 600may be comprised but not limited to a Switch CLI Handler 601, a SwitchSNMP Frame Handler 602, a FIA Controller Client 603, a FIA Switch ClientMain apparatus 604. The FIA Switch Client Main apparatus 604 mayinterface with the Switch Core Logic FIG. 9 304 to transmit to andreceive from the host switch communications ports. The FIA Switch ClientMain 604 apparatus may also interface with the Switch Frame ProcessingApparatus 606 to add, modify, or delete FMEs and ACLEs, get and clearstatistics counters, and add, modify, or delete Policies upon receipt ofcommands from a FIAC. The Switch CLI Handler 601 translates controlframes from the FIA Controller to the switch supported CLI. The SwitchSNMP Frame Handler 602 translates SNMP frames from the FIA Controller tocommands to and from the Switch Frame Processing Apparatus API 606. TheFIA Controller Client 603 may implement different protocols from the FIAController to control the switch including but not limited to a vendorspecific CLI over IP protocol, TCP/IP, OpenFlow Switch protocol, or aproprietary protocol. Further, the FIA Controller to Client protocolscan be encrypted.

FIG. 16 is a diagram showing the FIA Controller (FIAC) in more detail.The FIA Controller 650 may comprise the following modules: a FabricsServices Handler 651, a ACE & Frame Matching Filter Server 652, a FIPFrame Handler 653, a FIA Management Control Server 654, a FIA PolicyService 655, a Discovery Domain and Login Control Service 657, a FIAController a SNMP Handler 658, a State Change Notification Service 659,a FIA Web Server 660, a Name Service 661, an optional iSNS Client 665, amodified FCoE Controller 667, a FIA Controller Main 662, a FIACDatastore 680, and the FIA Network Interface 663. The FIA Controller 650may be implemented in software and reside in a physical server, in avirtual machine in a virtual server, in a communications switch, or in astorage array. The FIA Controller 650 can also be distributed over anumber of processors and servers. The FIA Network Interface 663 is thepath to the network over which FIA communication takes place 664. TheFabric Services Handler 651 receives frames destined for the well knownFabric Services Fibre Channel address identifiers. The Fabric ServicesHandler 651 operates on and responds to Fabric Services directedcommands which may include but not be limited to messages to the NameService and messages to the State Change Notification Service. The FIAController ACE & Frame Matching Filter Server 652 communicates with FIAsto add, modify, and remove both FMEs and ACLEs. The FIP Frame Handler653 operates on and responds to FIP frames in addition to originatestransmission of FIP frames. The FIP frames may include but not belimited to FIP FLOGI Request, FIP FLOGI LS_ACC, FIP FLOGI LS_RJT, FIPNPIV FDISC Request, FIP NPIV FDISC LS_ACC, FIP NPIV FDISC LS_RJT, FIPFabric LOGO, FIP Fabric LOGO LS_ACC, FIP Fabric LOGO LS_RJT, FIP KeepAlive, FIP Clear Virtual Links, FIP VLAN Request, FIP VLAN Notification,and FIP Vendor Specific frames. The FIA Management Controller Server 654may communicate with a FIA using a number of protocols, which mayinclude but not be limited to encapsulated CLI, SNMP, or proprietarytransport protocols. These protocols can further be encrypted. The FIAPolicy Service 655 binds certain Quality of Service elements to alogical link between two FCoE endpoints, two Fibre Channel endpoints, orFCoE and Fibre Channel endpoints. Since the FIA Controller manages theFrame Matching Filter entries, the FIA Controller can identify specificFCoE and/or Fibre Channel logical links and assign special forwardingpaths which contain specific flow priorities through PFC and ETScapabilities. The Discovery Domain and Login Control Service 657implements a mechanism to expose selected views of the Name Serverinformation to client devices or control frame delivery between devices.There are many methods to implement this capability, including FibreChannel zoning, Discovery Domains, and iSNS based Discovery Domains. TheFIA Controller SNMP Handler 658 operates on and responds to SNMP frames.These frames can be used to manage a FIA Controller or to communicatewith and control a FIA from the FIA Controller. The State ChangeNotification Service 659 operates on, responds, and generates messageswhen a state affecting a FCoE, Fibre Channel device, or FIA occurs. TheFIAC Web Server 660 provides external management capability to the FIAController 650. The Name Service 661 implements a Name Server thatprovides a way for FCoE and Fibre Channel device to register anddiscover Fibre Channel attributes. Once registered, the attributes aremade available to other FCoE and Fibre Channel devices within their sameDiscovery Domain or zone. The FIAC Datastore 680 may store the NameServer table, the Discovery Domain tables, the FIA and FIACconfiguration tables, and other information. The FIAC Datastore 680 maybe local to the FIAC or resident on another external CPU reachablethrough TCP/IP, SSH or another communications protocol. The FIACDatastore 680 may be comprised but not limited to a relational database,an object store database, in memory datastructures, or a flat filesystem. The MAC Datastore 680 may be coupled to a directory-enabledentity that may store client attributes in a Lightweight DirectoryAccess Protocol (LDAP) directory infrastructure, an Active Directory(AD) infrastructure, or in a distributed database. The iSNS Client 665is optional and is only present when an iSNS Server is used. Whenpresent, the iSNS Client 665 implements the iSNS Protocol andcommunicates with the iSNS Server. The FIAC 650 contains storagecomprising a FCF-MAC 668 used to receive FIP and certain FCoE framesfrom ENodes through FIAs.

FIG. 17 is a diagram showing a policy applied to two FCoE devices. AVN_Port, VN_Port1 701, instantiated in ENode1 700 is connected throughthe communications network 717 to VN_Port2 704, instantiated in ENode2703. The FIA Controller can add a Frame Matching entry to FIA Switch 1707 and FIA Switch 4 710 to tunnel 711 or 712 the communications betweenthe VN_Port's 701 702 as identified by the source and destinationEthernet MAC addresses and optionally the Fibre Channel addressidentifiers. The tunnel can be assigned certain quality of serviceelements such as Enhance Transmission service groups, priorities withinPer Flow Control, a TRILL or a SPB path. Tagging can be used in lieu oftunneling, tagging a frame comprising a VPLS, or a MPLS identifier. Asample Frame Matching Entry (FME) 718 added to FIA Switch 1 707 by a FIAController would match the incoming frame from ENode1 705 based on theFibre Channel destination address identifier, in case the symbolicVN_Port2 FCID. The resulting match action is to replace the sourceEthernet MAC address with the FCF-MAC address, FIACntrlMAC, and add atunnel that can be based on a number of methods which may comprise butnot be limited to VID replacement, MAC header addition (MAC-in-MAC),VLAN addition (QinQ), TRILL Shortest Path Bridging, VPLS, MPLS, or aspecial MAC replacement.

FIG. 18 is a diagram showing the Discovery Domain model. At the highestlevel are Discovery Domain Sets 750 751. Discovery Domain Sets 750 751are comprised of Discovery Domains 752 753 754 755. Discovery Domainsare themselves comprised of Discovery Domain Members 756 757 758 759760. Discovery Domain sets are uniquely identified, as are DiscoveryDomains. In the example in FIG. 18, Discovery Domain 1 752 is comprisedof WWN1 (Initiator 1) 756 and WWN2 (Target 1) 757. Discovery Domain 2753 is comprised of WWN3 (Initiator 2) 758 and WWN2 (Target 1) 757.Discovery Domain 3 754 is comprised of WWN2 (Target 2) 757 and WWN5(Initiator 3) 759. Discovery Domain 4 755 is comprised of WWN5(Initiator 3) 759 and WWN4 (Target 2) 760. FIG. 18 illustrates a bestpractice of allocating a zone or group to each Initiator/Target pair,i.e., Initiator 1 /Target 1, Initiator 2/Target 1, Initiator 3/Target 1,initiator 3/Target 2 as each are in a separate Discovery Domain and eachtarget is contained in a separate Discovery Domain Set. Further,Discovery Domains are assigned a Quality of Service metric, Platinum752, Gold 753, Silver 754, Best Effort 755. The Quality of Servicemetric may be applied to Lossless Ethernet based PFC classes, ETSgroups, network tunnels, network tags, or other methods. Configuring theQuality of Service metric may be done through the FIAC policy method.The Discovery Domain Sets 750 751 in FIG. 18 are each comprised ofDiscovery Domains comprising a specific target.

FIG. 19 is a diagram showing the FIA connection model. The diagram showsthe coupling of two FIA interconnection apparatus, FIA1 835 and FIA2 814with two ENodes, ENode H1 800 and ENode H2 811, two Fibre ChannelDevices, Fibre Channel Device 1 843 and Fibre Channel Device 2 819, twoFCoE Forwarding Devices (FCF) 804 840, and a FIAC 811. Physical links831 805 810 827 841 827 are Ethernet links and physical links 825 818are Fibre Channel links. Note the FCF1 804 and FCF2 840 can also be FCoEData Forwarder's (FDF) in this example. The Frame Processing Apparatus(FPA) in FIA1 825 and FIA2 925 comprise a list of Frame Match Entries(FMEs) 832 815 816 818 819 820 960 961 962 963 964 965 932 915 916 918919 920 970 971 972 973 974 975, all previously configured by an add FMEcommand received from the FIAC 811 by the FIAs 835 814. Note that ACLEand Policy entries are not shown in FIG. 19 for simplicity purposes.FME2 832 932 matches the FCID of VN_Port2 801, FME3 815 915 matches theFCID of VN_Port3, FME4 816 916 matches the FCID of VN_Port4 812, FME5818 918 matches the FCID of VN_Port5, FME6 819 919 matches the FCID ofN_Port6 844, and FME7 820 920 matches the FCID of N_Port7 820. FME8 960970 matches FIP frames with a destination Ethernet MAC address ofAll-ENode-MACs MAC address. FME9 961 971 matches FIP frames with thedestination Ethernet MAC address of All-FCF-MACs. FME10 962 972 matchesFIP frames with the destination Ethernet MAC address of the FIAC 811FCF-MAC address 841. FME11 963 973 matches FIP frames with a sourceEthernet MAC address of the FIAC 811 FCF-MAC address 841. FME12 964 974matches FCoE frames with a destination Ethernet MAC address of the FIAC811 FCF-MAC address 841. FME12 964 974 match entry is of a lowerpriority than the rest of the FME's meaning if another higher prioritymatch occurs, FME12's action(s) will not be executed. FME13 965 975matches FCoE frames with a source Ethernet MAC address of the FIAC 811FCF-MAC address 841. FME13 965 975 is of a higher priority than theother FME's meaning that if this FME matches an incoming frame, it'sactions will be executed in place of other lower priority FME matches.FME13 965 975 matches FCoE frames that have already had their source anddestination Ethernet MAC addresses substituted by the ingress FIA, i.e.,the rule matches frames in transit in intermediate and egress FIA's. Forexample for frames originating from VN_Port3 802 in ENode H1 800destined to VN_Port4 812 in ENode H2 811 they will match the FME4 816entry, i.e., the embedded Fibre Channel destination address identifierwill be the Fibre Channel address identifier of VN_Port4 812. FME4 816actions will replace the destination Ethernet MAC address by VN_Port4's812 Ethernet MAC address and the source address with the FIAC 811FCF-MAC address 841. The frame will be forwarded over the inter-FIA link829 based on the forwarding method used by the FIA's which couldcomprise RSTP, MSTP, OSPF, BGP, or any other layer 2 or layer 3forwarding method. The forwarding method may be independent of the FMEactions. Upon receipt of the frame by FIA 2 814, the entry FME13 975will match the frame, i.e., a high priority FME entry matching a FCoEframe with a source Ethernet MAC address of the FIAC 811 FCF-MAC address841. The action is to forward the frame.

Since the logical link 838 from VN_Port1 845 to VF_Port 850 utilizesFIA1 835 as a Lossless Ethernet Bridge, a FME for VN_Port1 is notcreated, FIA1 835 uses the Frame Filtering FIG. 9 308 table created byit's current method of frame forwarding, for example by RSTP, MSTP, etc.to forward the frame. FIA1 835 further functions as a Lossless Ethernetbridge to the logical link 837 created by the VE_Port 846 in FCF2 840and VE_Port 830 in FCF1 804. Fibre Channel N_Port7 820 in Fibre ChannelDevice 2 819 has a logical connection 809 with VN_Port5 806 in ENode H2811. The logical connection includes a Lossless Ethernet Port 808 on FIA2 814 and a Fibre Channel port 813 on FIA2 814. FCoE frames transmittedfrom VN_Port 5 806 to N_Port7 820 are identified by FME7 920 in FIA 2814. Fibre Channel frames transmitted from VN_Port 7 820 to VN_Port 5806 are identified by FME5 918. FCoE frames transmitted from VN_Port 3802 to VN_Port 4 812 are identified by FME4 816. FCoE frames transmittedfrom VN_Port 4 812 to VN_Port 3 802 are identifier by FME3 915. FCoEframes transmitted from VN_Port 2 801 to N_Port 6 844 are identified byFME6 819 and Fibre Channel frames transmitted by N_Port6 844 to VN_Port2801 are identified by FME2 832. FIAC 811 includes a modified FCoEController 812 and a FCF-MAC address 841. The modified FCoE Controller812 is adapted to receive and process FIP frames from ENodes, transmitFIP frames to ENodes, received and process certain FCoE frames fromENodes, VN_Ports, and N_Ports destined for well known Fibre ChannelFabric Services, and receive and process and transmit State ChangeNotification FCoE frames. The link 829 between FIA1 835 and FIA2 814 isa Lossless Ethernet link in which frames are forwarded by the FrameProcessing Apparatus in FIA1 835 and FIA2 814 respectively. Framestransmitted and received between the FIAs 829 may be forwardedcomprising but not limited to the following methods: RSTP, MSTP, TRILL,Shortest Path Bridging, OSPF, RIPng, and BGP. The virtual link 837between FCF1 804 and FCF2 840 is a VE_Port 846 to VE_Port 830inter-switch link and connects through FIA1 835. The virtual link 838between VN_Port 845 in ENode H1 800 and the VF_Port 850 in FCF2 840 is aVN_Port to VF_Port link. The VN_Port 845 to VF_Port 850 link 838 alsoconnects through FIA1 835. FIA1 835 behaves as a Lossless EthernetBridge for those specific virtual links 837 838. Further note that thereare no VE_Ports or E_Ports contained in the FIAs 835 814. The FIAconnection forwarding is based on a different method than the FC-SWrequired Fibre Channel FSPF routing method for FCF and FDF's.

FIG. 20 is a diagram showing the interconnection of two ENodes through anetwork of FIAs. FIG. 20 assumes the FIP Discovery and Login phases haveoccurred. Instantiated VN_Port1 1052 in ENode1 1029 transmits a FCoEframe 1020 to FIA 1 1028. The FCoE frame 1020 includes the destinationEthernet FCF-MAC address FIACntlrMAC 1025, the source Ethernet MACaddress, VN_Port1MAC 1024, the VLAN identifier VLAN1 1023, Data 1022,and a Frame Checksum 1021. The FCoE frame is received by FIA 1 1028. FIA1 1028 replaces the destination Ethernet MAC address with the MACaddress of VN_Port2 1015, the source Ethernet MAC address with FCF-MACaddress FIACntlrMAC 1014 and calculates a new FCS 1011. The modifiedFCoE frame 1010 is transmitted to FIA 2 1027. Upon receipt of the frame,FIA 2 1027 may forward the frame based on any number of forwardingmethods to FIA 3 1030. FIA 3 1030 receives the frame and forwards theframe to the destination VN_Port, VN_Port2 1053 with the original sourceand destination Ethernet. MAC addresses from the frame received from FIA2 1027.

FIG. 21 is a diagram showing the interconnection of two Fibre Channeldevices through a network of FIAs. Fibre Channel Device1 1181 isconnected to FIA 1 1178 over a Fibre Channel connection 1180. FibreChannel Device2 1182 is connected to FIA 3 1179 over a Fibre Channelconnection 1180. FIA1 is connected to FIA2 1177 over an Ethernet network1176. FIA2 1177 is connected to FIA3 1179 over an Ethernet network 1176.FIG. 21 assumes the FLOGI request and response interchange has occurred.N_Port 1 1191 contained in Fibre Channel Device 1 1181 transmits a FibreChannel frame 1170 addressed 1174 to N_Port 2 1192 contained in FibreChannel Device2 1182. FIA1 1178 receives the Fibre Channel frame,encapsulates it into a FCoE frame 1160, comprising a source Ethernet MACaddress of the internal MAC address of N_Port 1 NP1 MAC 1164 1187previously assigned by the FIA Controller and comprising a destinationEthernet MAC address of the internal MAC address of N_Port 2 NP2MAC 11651188 previously assigned by the FIA Controller (not shown). FIA 1 1178then forwards the FCoE frame 1160 to FIA2 1177. FIA2 1177 receives theframe and forwards the FCoE frame 1183 to FIA3 1179. FIA3 1179 receivesthe frame, decapsulates the frame into a Fibre Channel frame 1193 andtransmits it to Fibre Channel Device2 1182.

FIG. 22 is a ladder or sequence diagram showing a FIA Controller sendingFrame Matching Entries (FMEs) to a FIA. FIG. 22 assumes that the FIAController and FIA discovered and connected 1203. FIA and FIAC pairdiscovery can utilize any methods including but not limited to the LinkLevel Discovery Protocol, Service Level Protocol, DHCP, monitoring FIAController FIP Discovery Advertisements. The FIA Controller sends FME'sto FIA's to receive initialization and control frames from a network ofFLAs. The FIA Controller 1202 sends a FME 1204 frame comprising thefollowing match attributes: any source Ethernet MAC address,All-ENode-MACs destination Ethernet MAC address, Ethernet Type of FIP(FCoE Initialization Protocol). The action is to forward the frame. ThisFME allows FIP frames addressed to the address All-ENode-MACs to beforwarded to all connected ENodes. The FIA Controller 1202 sends a FME1205 frame comprising the following match attributes: any sourceEthernet MAC address, All-FCF-MACs destination Ethernet MAC address,Ethernet Type of FIP, with an action to forward the frame. This FMEallows FIP frames addressed to the address All-FCF-MACs to be forwardedto all connected FCFs. The FIA Controller 1202 is configured to receiveframes with the destination Ethernet MAC address of All-FCF-MACs 1210.The FIA Controller 1202 sends a FME 1206 frame comprising the followingmatching attributes: any source Ethernet MAC address, a destinationEthernet MAC address of the FCF-MAC address FIACntlrMAC 1209 (FIAController MAC), Ethernet Type of FIP with an action to forward theframe. This FME allows frames addressed 1209 to the FIA Controller 1202to be forwarded to the FIA Controller 1202. The FIA Controller 1202 thensends a FME to FIA 1 1201 comprising the following match attributes:source Ethernet MAC address of any, destination Ethernet MAC address ofFIA Controller FCF-MAC (FIACntlrMAC), an Ethernet Type of FCoE, a lowpriority and an action to forward the frame. This FME forwards FCoEframes from the FIA Controller if no other medium or high prioritymatches occur. The FIA Controller 1202 sends a FME to FIA 1 1201comprising the following match attributes: source Ethernet MAC addressof FIACntlrMAC FCF-MAC address, destination Ethernet MAC address of any,Ethernet Type of FIP, a medium priority for this FME with an action toforward the frame. This FME is for FIP frames sent by the FIA Controller1202 to ENodes and Fibre Channel devices. The FIAC sends a FME 1208 toFIA 1 1201 includes the following match attributes: source Ethernet MACaddress of FIACntlrMAC FCF-MAC address, destination Ethernet MAC addressof any, Ethernet Type of FCoE, a higher priority for this FME with anaction to forward the frame. This FME is for FCoE frames sent by the FIAController 1202 to attached ENodes and Fibre Channel devices.

FIG. 23 is a ladder or sequence diagram of the FIP Discovery frameexchange protocol between a FIA Controller and a FIA. ENode1 1225 sendsa FIP VLAN Request 1228 with the destination Ethernet MAC address ofAll-FCF-MACs to the connected FIA 1226. FIA 1 1226 forwards the framebased on a FME entry FIG. 22 1205 that was previously received from theFIA Controller 1227. The FIA Controller 1227 responds with a FIP VLANNotification 1230 message with the destination MAC address of ENode11225 and a source Ethernet MAC address of the FIA Controller. The frameis forwarded by FIA 1 1226 using a previously set FME, FIG. 22 1211, tothe destination ENode1 1225. The FIA Controller 1227 transmits a FIPDiscovery Advertisement frame 1231 with the destination Ethernet MACaddress of All-ENode-MACs and the source Ethernet MAC address of the FIAController (HACntrlMAC). The frame is forwarded by FIA 1 1226 to ENode11225. ENode1 1225 transmits a unicast FIP Discovery Solicitation frame1232 with the destination Ethernet MAC address of the FIA Controller andthe source Ethernet MAC address of the ENode 1 1225 (ENode1MAC). FIA 11226 forwards the frame to the FIA Controller 1227 which responds with aunicast FIP Discovery Solicitation frame 1234 with the destinationEthernet MAC address of ENode1 1225 (ENode1MAC) and the source EthernetMAC address of the FIA Controller FCF-MAC address 1227 (FIACntlrMAC).

FIG. 24 is a ladder or sequence diagram showing a FIP FLOGI Request, FIPFLOGI LS_ACC frame exchange. ENode1 1250 transmits a FIP FLOGI Requestframe 1253 comprising a destination Ethernet FCF-MAC address of the FIAController (FIACntrlMAC) and a source Ethernet MAC address of the ENode1FCoE_Controller (ENode1MAC), FIG. 7 214. FIA 1 1251 receives the FIPFLOGI Request and forwards the frame based on a previously assigned FME,FIG. 22 1206, that matches the frame destination Ethernet MAC address ofthe FIACntlrMAC FCF-MAC address and the Ethernet Type of FIP. The FIAController 1252 assigns a MAC address and a Fibre Channel addressidentifier for the newly instantiated VN_Port 1250. The FIA Controller1252 adds a FME 1255 to all FIAs in the Discovery Domain of the VN_Port,including the local FIA switch 1251. The FME includes the followingmatch fields: source Ethernet MAC address of any, destination EthernetMAC address of any, Ethernet Type of FCoE, the Fibre Channel DestinationAddress Identifier (DID) in the embedded FCoE frame is the newlyassigned Fibre Channel address identifier, in this case the symbolicVN1FCID, with an action to replace the destination Ethernet MAC addresswith the newly assigned VN_Port MAC, in this case the symbolic VN1MAC,replace the source Ethernet MAC address with the FIA Controller FCF-MACaddress (FIACntlrMAC), and forward the frame.

FIG. 25 is a ladder or sequence diagram showing the exchange of a FIPNPIV FDISC/FIP LS_ACC message exchange between an ENode and a FIAController. The ENode 1300 transmits a FIP NPIV FDISC frame 1305 withthe destination Ethernet MAC address of the FIA Controller FCF-MACaddress (FIACntlrMAC) and a source Ethernet MAC address of theFCoE_Controller (ENode1MAC). FIA 1 1301 forwards the frame based on thepreviously assigned FME, FIG. 22 1206, that matches the framedestination Ethernet MAC address of the FIACntlrMAC FCF-MAC address andthe Ethernet Type of FIP. The FIA Controller 1302 assigns a MAC addressand a Fibre Channel address identifier for the newly instantiatedVN_Port 1300. The FIA Controller 1302 adds a FME entry 1306 to all FIAsin the Discovery Domain of the VN_Port, including the local FIA switch1301. The FME includes the following match fields: source Ethernet MACaddress of any, destination Ethernet MAC address of any, Ethernet Typeof FCoE, the Fibre Channel Destination Address Identifier (DID) in theembedded FCoE frame is the newly assigned Fibre Channel addressidentifier, in this case the symbolic VN2FCID. The action upon framematch is to replace the destination Ethernet MAC address with the newlyassigned VN_Port MAC, in this case the symbolic VN2MAC, replace thesource Ethernet MAC address with the FIA Controller FCF-MAC address(FIACntlrMAC), and forward the frame.

FIG. 26 is a ladder or sequence diagram showing the exchange of a FCoEState Change Registration request and LS_ACC response message exchangein addition to a Name Server query request and response messageexchange. VN_Port1 of ENode1 1400 transmits a FCoE SCR Request message1402 with a destination Ethernet MAC address of the FIA ControllerFCF-MAC address (FIACntlrMAC), a source Ethernet MAC address of thetransmitting VN_Port (VN1MAC), a Fibre Channel destination addressidentifier (DID) of the well known Fabric Controller (FFFFFDh) and theFibre Channel source address identifier (SID) of the VN_Port1 (VN1FCID).The State Change Registration ELS Request (SCR) requests the FabricController to add the VN_Port that is sending the SCR Request to thelist of VN_Port/Nx_Ports registered to receive the RSCN (Register StateChange Notification) ELS frames. FIA 1 receives the FCoE SCR frame andforwards it to the FIA Controller 1401. The FIA Controller FabricServices Frame Handler, FIG. 15 651, services the frame and transmits aFCoE LS_ACC Response 1404 comprising a destination Ethernet MAC addressof the VN_Port (VN1MAC) and a source Ethernet MAC address of the FIAController FCF-MAC address 1401 (FIACntlrMAC). VN_Port1 of ENode1 1400transmits a Name Server query, Get Port Identifiers (GID_FT) request1405 to return all Port Identifiers having registered support for thespecified FC-4 TYPE. The FIA Controller 1401 queries the internal NameServer for all registered FC-4 TYPEs visible, i.e., in the sameDiscovery Domains, as querying VN_Port1. The FIA Controller 1401 returnsa FCoE LS_ACC 1408 to VN_Port1 1400 which may comprise a list of FibreChannel Port Identifiers.

FIG. 27 is a ladder or sequence diagram showing a PLOGI exchange betweenENodes. VN_Port1 of ENode1 1500 transmits a FCoE PLOGI request 1505 witha source Ethernet MAC address of the VN_Port1 (VN1MAC), a destinationEthernet MAC address of the FIA Controller 1502, a Fibre Channel sourceaddress identifier (SID) of VN_Port1 (VN1FCID), and a Fibre Channeldestination address identifier (DID) of VN_Port100 (VN100FCID) containedin ENode2 1504. FIA1 1501 matches the frame with the FME 1508 matchfields comprising the source and destination Ethernet MAC addresses ofany, the Ethernet Type of FCoE, the Fibre Channel destination addressidentifier (DID) of VN_Port100 (VN100FCID). The action is to replace thedestination Ethernet MAC address with VN_Port100's MAC address (VN100MAC), the source Ethernet MAC address with the FIA Controller FCF-MACaddress (FIACntlrMAC), and to forward the frame. The frame is forwardedto FIA 7 1503. Note that once the FIP sequence is complete and theframes are not destined for Fabric Services well known addresses, theFIA Controller 1502 is not involved in processing the frames, i.e.,receiving the frame and forwarding the frame. FIA 7 1503 receives theFCoE PLOGI frame and forwards the frame based on the previously assignedFME comprising the matching fields of source Ethernet MAC address of theFIA Controller FCF-MAC address 1502 (FIACntlrMAC), a destinationEthernet MAC address of any, an Ethernet Type of FCoE, and action isforward the frame. VN_Port100 of ENode2 1504 receives the FCoE PLOGI andresponds with a FCoE LS_ACC to the PLOGI 1515. The FCoE LS_ACC includesa destination Ethernet MAC address of the FIA Controller FCF-MAC address(FIACntlrMAC), a source Ethernet MAC address of VN_Port100 (VN100 MAC),a Fibre Channel destination address identifier (DID) of VN_Port1(VN1FCID), and a Fibre Channel source address identifier if VN_Port100(VN100FCID). FIA 7 1503 uses the previously assigned FME 1517 comprisingthe match fields of source and destination Ethernet MAC address of any,the destination Fibre Channel address identifier (DID) of VN_Port1(VN1FCID), and the Ethernet Type of FCoE, and with an action to replacethe destination Ethernet MAC address with VN_Port1's MAC address(VN1MAC), replace the source Ethernet MAC address with the FIAController 1502 FCF-MAC address (FIACntlrMAC), and forward the frame.The frame is forwarded 1514 to FIA 1 1501 which matches the frame withthe FME 1516 comprising the match fields of the source Ethernet MACaddress of the FIA Controller 1502 FCF-MAC address (FIACntlrMAC), thedestination Ethernet MAC address of any, the Ethernet Type of FCoE, withan action to forward the frame to VN_Port1 in ENode1 1500.

FIG. 28 is a ladder or sequence diagram showing an ENode and a VN_Porttransmitting a FIP Keep Alive frames. FIG. 28 further shows the FIAController 1552 transmitting a FIP Discovery Advertisement frame 1556.ENodes and VN_Ports transmit FIP Keep Alive frames on specifiedintervals to signal the FCF, in this example the FIA Controller thatthey are still reachable. FIA 1 1551 forwards the frames based on apreviously assigned FME to forward frames with the destination EthernetMAC address of the FIA Controller FCF-MAC address (FIACntlrMAC) and theEthernet Type of a PIP frame. The FIA Controller 1552 transmits FIPDiscovery Advertisement frames 1556 addressed to All-ENode-MACs toadvertise the MAC address and the reachability of the FIA Controller1552. FIA 1 1551 forwards the FIP Discovery Advertisement frames basedon a previously assigned FME forwarding based on the destinationEthernet MAC address of All-ENode-MACs and the Ethernet frame Type ofFIP.

FIG. 29 is a sequence or ladder diagram showing the initialization of aFIA Controller utilizing an iSNS Server for State Change Notification,Discovery Domain, and Name Services. The Internet Storage Name Service(iSNS) Protocol (iSNSP) is used for interaction between iSNS Server 1602and the FIA Controller 1601. In this exemplary invention, the iSNSServer 1602 has been adapted to facilitate automated discovery,management, and configuration of FCoE and Fibre Channel devices in anetwork of FIAs. An iSNS Server provides intelligent storage discoveryand management services comparable to those found in Fibre Channelnetworks. Since an iSNS Server is currently adapted to only discoveryand manage iSCSI and iFCP devices, in the current exemplary invention,the RAE translates and adapts the messages to and from the iSNS Serverto make it useful for a repository of currently active FCoE and FibreChannel nodes and related attributes. The FCoE and Fibre Channel nodescommunicate to a FIA Controller 1601 which in turn may communicate tothe iSNS Server 1602. In the exemplary invention, the FIA may translatecertain FIP, FCoE, and Fibre Channel commands that are directed to FibreChannel Fabric Services into iSNS commands and responses, i.e., there isnot direct communication between ENodes, Fibre Channel nodes, FIAs andthe iSNS Server. By translating the commands and responses, this allowsan iSNS Server to manage a dynamic database of the FCoE and FibreChannel devices, through a FIA Controller, and related information thatare currently available on the network. The database helps provide FCoEand Fibre Channel target discovery functionality for the FCoE and FibreChannel initiators on the network, through a FIA and a RAC. The databaseis kept dynamic by using the Registration Period and Entity StatusInquiry features of iSNS. Registration Period allows the server toautomatically deregister stale entries. Entity Status Inquiry providesthe server a capability similar to ping to determine whether registeredclients, i.e., FIA and the ENodes they are connected to, are stillpresent on the network, and allows the server to automaticallyderegister those clients which are no longer present. The iSNS Serveralso supports a State Change Notification Service, allowing registeredclients to be made aware of changes to the database in the iSNS server.The iSNS Server database is the information repository for iSNS Servers.It maintains information about iSNS client attributes. Adirectory-enabled implementation of iSNS may store client attributes ina Lightweight Directory Access Protocol (LDAP) directory infrastructure.The iSNS Server provides a name registration service function to allowall entities through a FIA Controller in a storage network to registerand query the iSNS database. Both targets and initiators can register,translated by a FIA Controller, in the iSNS database, as well as queryfor information about other initiators and targets. This allows, forexample, a client initiator to obtain information about target devicesfrom the iSNS server. This service is modeled on the Fibre ChannelGeneric Services Name Server described in Internet Engineering TaskForce (IETF) request for comment (RFC) documents, with extensions,operating within the context of an IP network. The iSNS Server providesa Discovery Domain (DD) service, similar to zones in a Fibre Channelfabric, facilitating the partitioning of FCoE and Fibre Channel devicesinto manageable groupings for administrative and logon control purposes.It allows the administrator to limit the logon process of each FCoE andFibre Channel host through a FIA Controller to the more appropriatesubset of targets registered in the iSNS Server. Devices can be membersof multiple DDs. Logon control allows targets to delegate their accesscontrol or authorization policy to the iSNS server. The target node ordevice downloads, through a FIA, the list of authorized initiators fromiSNS. Each node or device is uniquely identified. Only initiators thatmatch the required identification and authorization provided by the iSNSwill be allowed access by that target node during session establishment.DDs can be managed offline by using a separate management computer thatis using the iSNS Protocol or SNMP or communicates to a FIA Controllerwhich in turn communicates with the iSNS Server. Valid and activediscovery domains belong to at least one active DDS. Discovery domainsthat do not belong to an activated DDS are not enabled. The iSNS servermaintains the state of DD membership for all FCoE and Fibre Channeldevices, even for those devices that have been deregistered. DDmembership is persistent regardless of whether a FCoE or Fibre Channeldevice is actively registered in the iSNS database. The State ChangeNotification (SCN) service allows the iSNS Server to issue notificationsto FIA Controllers about network events that affect the operationalstate of storage nodes. FIA Controllers may translate the iSNS ServerState Change Notification messages into FCoE and Fibre Channel basedState Change Notification messages. A FCoE or Fibre Channel initiatorsends name server queries to a FIA Controller, which may translate themessages and query the iSNS Server to discover FCoE and Fibre Channeltarget devices. A management station may use iSNS to monitor storagedevices and enable or disable storage sessions by configuring discoverydomains. A management station usually interacts with the iSNS Server asa control node with access to all iSNS database records and privilegesto modify discovery domains. Through manipulation of discovery domains,the management station controls the scope of device discovery for FCoEand Fibre Channel devices that query the iSNS server through a FIAController.

Referring to FIG. 29, the FIA Controller 1601 discovers the presence1603 of the iSNS Server 1602. There are several methods of discoverythat the FIA Controller 1601 can utilize. They include using the ServiceLocation Protocol (SLP, see RFC 2608) that provides a flexible andscalable framework for providing FIA Controllers with access toinformation about the existence, location, and configuration ofnetworked services, including the iSNS Server. Another method of iSNSServer IP address discovery can be through the stored value in a DHCPserver, where it can be downloaded by FIA Controller. A further methodof iSNS Server discovery is to monitor by the FIA Controller for iSNSServer heartbeat broadcasts. This can also notify FIA Controllers of theexistence of more than one iSNS Server, for example for backup iSNSServers. Upon discovery of the iSNS Server, a FIA Controller transmits aDevice Attribute Registration Request (DevAttrReg) 1604 to the iSNSServer which may register new objects which may include but not belimited to it's Portal IP address, TCP/UDP Port, Entity Status Inquiry(ESI) Interval and Port, Fibre Channel Port Name of the FIA Port, FibreChannel address identifier. The iSNS Server 1602 receives the DevAttrRegRequest 1604, updates the iSNS database for this FIA Controller andresponds with a Device Attribute Registration Response (DevAttrRegRsp)1605 message. One of the attributes of the DevAttrRegRsp 1605 message isthe Entity Identifier (EID) that uniquely identifies each Network Entityregistered in the iSNS Server. The FIA Controller 1601 transmits a SCNRegister Request (SCNReg) 1609 message to the iSNS Server 1602 to allowthe FIA Controller 1601 to register to receive State Change Notification(SCN) messages. The SCN message notifies a FIA of changes to any otherremote FIA attached devices (i.e., ENodes or Fibre Channel Devices)within any Discovery Domain of which it is a member. The DiscoveryDomain (DD) facilitates the partitioning of FIA attached devices (ENodesand Fibre Channel Devices) into more manageable groupings foradministrative and login control purposes. It allows the administratorto limit the login process of each ENode or Fibre Channel Device to themore appropriate subset of devices registered in the iSNS ServerDatabase. The devices are usually storage targets. This service issimilar to Fibre Channel zoning, where zones are created composed ofrelated devices, such as initiator target pairs, providing security toexclude non-administratively configured devices. A Request FC_DOMAIN_ID(RqstDomId) message 1612 is sent from the FIA Controller 1601 to theiSNS Server 1602. The RqstDomId message 1612 is used to allocatenon-overlapping FC_DOMAIN_ID values. The FC_DOMAIN_ID value is storedFIA Controller 1601 resident storage. The iSNS Server 1602 becomes theaddress assignment authority for the entire FIA fabric. After receipt ofthe Request FC_DOMAIN_ID Response (RqstDomIdRsp) 1613 from the iSNSServer 1602, the FIA Controller 1601 then sends a FIP DiscoveryAdvertisement frame 1617 to start the discovery protocol to findattached ENodes. The FIP Discovery Advertisement frame 1617 is receivedby the FIA 1617 which forwards the frame to ENode1 1600. Further in FIG.28, The DevAttrReg 1604, DevAttrRegRsp 1605, SCNReg 1609, SCNReg Rsp1611, RqstDomID 1612, and RqstDomID Rsp 1613 messages are all IP 1610encapsulated iSNS messages.

FIG. 30 is a ladder or sequence diagam showing the interaction betweenan ENode, a FIA Controller, an iSNS Server, and a remote ENode upon theexchange of FLOGI/LS_ACC FCoE frames. ENodel 1650 transmits a FIP FLOGIRequest frame 1654 to the FIA 1666. The FIA 1666 forwards the frame tothe FIA Controller 1651. The HA Controller 1651 allocates a new MACaddress and a new Fibre Channel address identifier. The FIA Controller1651 then transmits a DevAttrReg request 1655 comprising the new MACaddress and the new Fibre Channel address identifier to the iSNS Server1652. The iSNS Server 1652 updates its internal database with the newinformation. FIG. 30 assumes that VN_Port2 in ENode2 1653 has previouslyinitialized, registered into the name server table, and is in the sameDiscovery Domain as VN_Port1 1650, The iSNS Server 1652 sends a StateChange Notification message to the FIA Controller 1651 which in turntranslates the message into a Fibre Channel State Change Notificationmessage and transmits it to the FIA 1617 which forwards the frame toENode2 1662. ENode2 1662 transmits the RSCN response message 1665 backto the HA Controller 1651. The FIA Controller 1651 transmits a LS_ACCFIP frame 1659 to the FIA 1666 in response to the FIP FLOG requestframe, which in tuna forwards the frame to the ENodel 1650, completingthe FIP FLOGI/LS_ACC frame exchange.

FIG. 31 is a ladder or sequence diagram showing the initialization anddiscovery between two ENodes using the FIA Controller and iSNS Server,VN_Port1 1700 transmits a FCoE PLOGI frame 1705 to login to the FabricDirectory Servicer. FIA 1701 forwards the frame to the FIA Controller1702. The FIA Controller 1702 transmits a FCoE LS_ACC response 1706.VN_Port1 1700 transmits a FCoE GID_FT name services query 1708 to theName Server. FIA 1701 receives the frame and forwards it to the FIAController 1702 based on a previously assigned FME. The FIA Controller1702 transmits a DevAttrReg request 1711 to the iSNS Server 1703requesting information about all FC4-TYPEs of FCP which are in theDiscovery Domain of VN_Port1 1700. The iSNS Server 1703 returns aDevAttrReg response with a list of Fibre Channel port or addressidentifiers identifying which VN_Ports with the same FCP-TYPE arevisible to VN_Port1 1700. The FIA Controller 1702 translates theDevAttrReg response message 1713 into a FCoE LS_ACC message 1714 andtransmits the message to the FIA 1701. The FIA 1701 receives the messageand forwards it to the VN_Port1 1700. In this example, the FCoE LS_ACCresponse message 1714 contains the Fibre Channel address identifier forVN_Port2 1704. VN_Port1 1700 transmits a FCoE PLOGI request message 1716comprising the source Ethernet MAC address of VN_Port1 (VN1MAC) 1716,the destination Ethernet MAC address of the FIA Controller FCF-MACaddress (FIACntlrMAC) 1702, a destination Fibre Channel addressidentifier (DID) of VN_Port2 (VN2FCID), and a source Fibre Channeladdress identifier (SID) of VN_Port1 (VN1FCID) 1700. FIA 1701 receivesthe FCoE PLOGI, substitutes the destination Ethernet MAC address ofVN_Port2 (VN2MAC) 1704 and substitutes the source Ethernet MAC addressof the FIA Controller FCF-MAC address (FIACntlrMAC) 1702 and forwardsthe frame to VN_Port2 1704.

FIG. 32 is a ladder or sequence diagram showing the interconnection oftwo native Fibre Channel devices through FIAs with ports adapted toconnect to Fibre Channel devices. FIA 1 1801 and FIA 2 1803 compriseports adapted to connect to Fibre Channel devices 1805 1807, FIA 1 1801and FIA 2 1803 also comprise ports adapted to connect to Ethernet 1806.Fibre Channel Device 1 1800 transmits a Fibre Channel FLOGI requestframe 1808 to FIA1 1801. The Fibre Channel FLOGI frame includes adestination Fibre Channel address identifier of the Directory Service(FFFFFCh), which is implemented within the FIA Controller 1802. FIA 11801 receives the Fibre Channel FLOGI frame, encapsulates it into a FCoEframe comprising a source Ethernet MAC address of the Fibre ChannelDevice (FCD1MAC) and destination Ethernet MAC address of the FIAController FCF-MAC address (FIACntlrMAC) 1802. The Fibre Channel DeviceMAC address is assigned to the Fibre Channel Device 1800 and representsa virtual FCoE_Controller MAC address. This MAC address is only usedinternally for frames between FIAs and between FIA and FIA Controllersand is not used for FIA to Fibre Channel Device communications over aFibre Channel link 1805 1807. FIA 1 1801 forwards the FCoE encapsulatedFibre Channel FLOGI frame to the FIA Controller 1802. The FIA Controller1802 services the frame and returns a FIP LS_ACC response frame 1812comprising the source Ethernet FCF-MAC address of the FIA Controller(FIACntrlMAC) 1802, the destination Ethernet MAC address of the FibreChannel Device (FCD1MAC), the source Fibre Channel address identifier ofthe Directory Service (FFFFFCh), and the newly assigned destinationFibre Channel address identifier of the Fibre Channel Device N_Port1(VN1FCID). FIA 1 1801 receives the LS_ACC FCoE frame, decapsulates theframe into a Fibre Channel frame and transmits the Fibre Channel frame1811 to Fibre Channel Device 1 1800. N_Port1 in Fibre Channel Device 11800 transmits a Fibre Channel PLOGI request frame 1816, addressed toN_Port2 (FCD2FCID) 1804. FIA 1 1801 receives the Fibre Channel PLOGIframe, encapsulates the frame into a FCoE PLOGI frame 1818 comprising asource Ethernet MAC address of N_Port1 (NP1MAC) 1800 and a destinationEthernet MAC address of N_Port2 (NP2 MAC) 1804. FIA 1 1801 then forwardsthe frame 1818 to FIA 2 1803. FIA 2 1803 receives the frame,decapsulates the frame into a Fibre Channel frame and transmits theresulting frame 1820 to N_Port2 in Fibre Channel Device 2 1804. N_Port2in Fibre Channel Device 2 1804 transmits a Fibre Channel LS_ACC responseframe 1821 to the Fibre Channel PLOGI frame. FIA 2 1803 receives theframe, encapsulates the frame into a FCoE frame, comprising a sourceEthernet MAC address of N_Port2 (NP2MAC), a destination Ethernet MACaddress of N_Port1 (NP1MAC). FIA 2 1803 transmits the frame to FIA 11801. FIA 1 1801 decapsulates the FCoE frame into a Fibre Channel frameand transmits the Fibre Channel frame 1817 to N_Port1 in Fibre ChannelDevice 1 1800.

FIG. 33 is a ladder or sequence diagram showing the communicationbetween a ENode and a Fibre Channel Device through FIAs. The connectionsbetween the ENode1 1850, the FIA 1 1851, the FIA Controller 1852, and atleast one port in FIA 2 1853 are Ethernet connections 1855. Theconnection between FIA 2 1853 and the Fibre Channel Device 1854 is aFibre Channel connection 1856. VN_Port1 in ENode1 1850 transmits a FCoEPLOGI request 1857 frame comprising the source Ethernet MAC address ofVN_Port1 (VN1MAC) 1850, destination Ethernet MAC address of N_Port1(NP1MAC, not used over Fibre Channel links), a destination Fibre Channeladdress identifier (DID) of N_Port1 (NP1FCID), and a source FibreChannel address identifier (SID) of VN_Port1 (VN1FCID). FIA 1 1851receives the frame, replaces the source Ethernet MAC address with theFIA Controller FCF-MAC address (FIACntlrMAC) 1852 and replaces thedestination Ethernet MAC address with N_Port 1's MAC address (NP1MAC),then transmits the frame 1858 to FIA 2 1852. FIA 2 1852 receives theframe, decapsulates the frame into a Fibre Channel frame 1860 andtransmits the Fibre Channel PLOGI frame to N_Port1 in Fibre ChannelDevice 1 1854. N_Port1 1854 transmits a Fibre Channel LS_ACC frame tothe PLOGI frame 1861. FIA 2 1852 receives the frame and encapsulates itinto a FCoE LS_ACC frame, then transmits the frame 1864 to FIA 1 1851,FIA 1 1851 receives the frame from FIA 2 1852, then forwards the frameto VN_Port1 in ENode1 1850.

FIG. 34 is a diagram showing multiple virtual connections between aENodes, and FCFs. ENode1 1919 includes three VN_Ports, VN_Port1 1916,VN_Port2 1917, and VN_Port3 1918, ENode2 1904 includes VN_Port2 1941.VN_Port2 1917 is in a virtual connection over VID 20 1914 with VN_Port21941 in ENode2 1904 connected through FIA 1903. VN_Port1 1916 is in avirtual connection over VID 10 1915 with VF_Port 1901 in FCF1 1900.VN_Port3 1918 is in a virtual connection over VID 30 1912 with VF_Port1907 in FCF 1906. FCF2 1906 is connected to a Fibre Channel Switch 1908which is in turn connected to 1910 FC Device3 1911. VN_Port3 1918communicates with FC Device3 1911 through the VF_Port 1907 in FCF2 1096.Both VN_Port1 1916 and VN_Port3 1918 in ENode1 1919 communicate to FCF11900 and FCF2 1906 through the FIA 1903. FIG. 34 illustrates thecapability of an FIA to forward FIP and FCoE frames in separate VID'sbetween ENodes and FCF/FDFs. Further FIA 1903 can also restrict FIPdiscovery from select FCF/FDFs and from ENodes by a number of methodscomprising but not limited to: filtering FIP Discovery Advertisementsand FIP Discovery Solicitations by the source Ethernet MAC address orspecific descriptors within the frame comprising: the priority, MACaddress, Name_Identifier, and Fabric descriptors. FIA 1903 can alsorestrict FIP discovery to and from ENodes by selectively filtering PIPDiscovery Advertisements and FIP Discovery Solicitations transmitted toand received from ENodes by a FIA.

FIG. 35 is a ladder or sequence diagram showing the FIP Discoveryprotocol exchange between an ENode, a FIA Controller, and a FCF. FIAController 2001 transmits a FIP Discovery Advertisement frame 2005comprising the source Ethernet MAC address of the FIA Controller FCF-MACaddress (FIACntlrMAC) 2006, the destination Ethernet MAC address ofAll-ENode-MACs 2007, a VID of 10 2008, a priority of 10 2015 and asymbolic Name_Identifier of JedaNetworks. FIA 1 2003 receives the frameand forwards it to ENode1 2000. Enode1 2000 uses the information fromthe FIP Discovery Advertisement frame 2005 to build a list of availableFCF-MACs 2034. The list includes but is not limited to the FIAController FCF-MAC address (FIACntlrMAC), the priority, the VID 2035.FCF1 2002 transmits a FIP Discovery Advertisement frame 2010 comprisingthe source Ethernet MAC address of the FCF (FCFMAC) 2011, thedestination Ethernet MAC address of All-ENode-MACs 2012, a VID of 202013, a symbolic Name_Identifier of Sisco 2014 and a priority value of12 2017. FIA 1 2003 receives the frame and forwards it to ENode1 2000.FIA 1 may also be configured to not forward the frame. Not forwardingthe frame will isolate FCF1 2002 with ENode1 2000 which may bedesirable, ENode1 2000 receives the forwarded FIP DiscoveryAdvertisement frame 2010 and adds another entry into the ENode1 FCF List2028. The entry 2037 includes but is not limited to the FCF MAC(FCFMAC), the priority 12, and the VID 20. ENode 1 2000 responds to thefirst FIP Discovery Advertisement frame 2005 with a unicast FIPSolicitation frame 2020 comprising a destination Ethernet MAC address ofthe FIA Controller FCF-MAC address (FIACntlrMAC), a source Ethernet MACaddress of the ENode1 FCF-Controller MAC (ENode1MAC), and a VID of 10.The frame is received by FIA 1 2003 and forwarded to the FIA Controller2001. ENode 1 2000 responds to the second FIP Discovery Advertisementframe 2010 with a unicast FIP Solicitation frame 2024 comprising adestination Ethernet MAC address of the FCF-MAC (FCFMAC), a sourceEthernet MAC address of the ENode1 FCF Controller MAC (ENode1MAC), and aVID of 10. The frame is received by FIA 1 2003 and forwarded to the FIAController 2001. A FIP Discover Advertisement frame 2015 with a VID 100and a Name_Identifier of Saturn is transmitted from FCF2 2004. The FIPDiscovery Advertisement is discarded 2039 by FIA1 2003 by a FME thatidentifies the specific FIP Discovery Advertisement frame. Discardingthe FIP Discovery Advertisement will prevent the frame from reachingENode1 2000 thereby isolating FCF2 2004 from ENode1 2000. The resultingENode1 FCF List 2028 includes entries for all 2036 2037 of the FCF-MACs,including the FCF1 2002 and FIA Controller 2001, ENode1 2000 may loginto all FCF-MACs including the FIA Controller 2001 and the FCF 2002 andquery the Name Servers. It is possible that the same device (ENode orFibre Channel device) is in multiple Name Server tables in multipleFabrics. ENode1 2000 may choose to login (PLOGI) to the device throughthe FCF or FIA Controller with the highest priority. This method allowsfor a single connection to a device that's resident in multiple NameServer tables, ENode1 2000 may also choose to login (PLOGI) to thedevice through lower priority FCF or FIA Controllers if the primaryconnection fails.

FIG. 36 is a diagram showing an ENode determining the path to a remotedevice. The ENode discovers that multiple FCF and/or FIA Controller'sare reachable 2041. The ENode logs into and queries all Name Servers2042 coupled to the FCF-MACS. If a remove device (ENode) is reachablethrough a single FCF-MAC the ENode transmits a PLOGI to the remotedevice through the single FCF-MAC 2046. If the target is reachablethrough more than one FCF-MAC the ENode sends a PLOGI to the FCF-MAChaving the highest priority 2047 attribute from the previously receivedFIP Discovery Advertisement frame.

FIG. 37 is a diagram showing the generation of FMEs upon the receipt ofa FIP FLOGI or FIP NPIV FDISC frame. The FIA Controller receives a FIPFLOGI or a FIP NPIV FDISC frame 2051. The FIA Controller assigns a newMAC address and a new Fibre Channel address identifier 2052. If theaddress assignment is not successful 2053, a FIP LS_RJT response frameis transmitted 2056. If the address assignment is successful 2054, theFIA Controller sends a Frame Match Entry (FME) to all connected FLAswith a medium priority, the match fields comprising a source anddestination Ethernet MAC address of any, a Ethernet Type of FCoE, aFibre Channel destination address identifier (DID) of the newly assignedFibre Channel address identifier (newFCID), and with an actioncomprising, substitute the source Ethernet MAC address with the FIAController FCF-MAC address (FIACntlrMAC), substitute the destinationEthernet MAC address with the newly assigned Fibre Channel MAC address(newMAC), and forward the frame. The Name Server is updated with thenewly assigned addresses and any devices within the same DiscoveryDomains are notified of a change by transmitting a RSCN 2058. The AccessControl List Entries for the FIAs are updated 2059 and a FIP LS_ACCresponse frame is then transmitted 2057.

FIG. 38 is a diagram showing the removal of FMEs upon the receipt of aFIP FLOGO frame. The FIA Controller receives a FIP FLOGO frame 2076. TheFIA Controller deassigns the specified MAC address and specified FibreChannel address identifier 2077. If the address de-assignment is notsuccessful 2078, a FIP LS_RJT response frame is transmitted 2081. If theaddress de-assignment is successful 2078, the FIA Controller sends amessage to remove the Frame Match Entry (FME) to all connected FIAs thatmatches the priority, match fields, and actions of the specified FME2080. The Name Server is updated and RSCNs are transmitted for alldevices in the same Discovery Domain 2107. The access control listentries for all FIAs are updated 2108. A FIP LS_ACC response frame isthen transmitted 2082.

A myriad of frame forwarding methods can be used within FIAs. Since theforwarding function is separated from other FIA Controller functions anynetwork available forwarding method can be used. This is different fromFCF routing which uses the FSPF routing method. The forwarding and/orrouting methods that a FIA can utilize includes but is not limited toSTP, RSTP, MSTP, Shortest Path Bridging, MPLS, VPLS, TRILL, OSPF, BGP,RIP. IEEE 802.1aq Shortest Path Bridging and the IETF effort calledTransparent Interconnection of Lots of Links (TRILL) have been createdthat mitigate the disadvantages of the Spanning Tree Protocol basedforwarding methods.

Routing Bridges or RBridges, have been created to implement the TRILLprotocol. FIG. 39 is a network diagram showing the interconnection ofRouter Bridges (RBridges) 2210 2214. The diagram shows a first RBridge,RBridge 1 2210 connected 2211 to an Ethernet Cloud or network 2212 thatis connected 2213 to a second RBridge, RBridge 2 2214. RBridges can beinterconnected using any layer 2 technology such as IEEE 802.3, shown inFIG. 40 or some other link technology such as PPP, see RFC1661. TheEthernet Cloud or network 2212 may include but not be limited to hubs,point-to-point or shared media, IEEE 802.1D bridges, 802.1Q bridges, ormetropolitan area networks such as those described by the ProviderBackbone Bridge Traffic Engineering (PBB-TE) networking standard, IEEE802.1Qay-2009 or Provider Backbone Bridges (PBB), IEEE 802.1ah. RBridgeports make use of IEEE 802.1Q port VLAN and priority processing. Inaddition, the Ethernet Cloud 2212 may implement other lower level 802.1protocols as well as protocols for the link in use, such as PAUSE,Priority Based Flow control, port based access control (802.1X), MACsecurity (802.1AE), or link aggregation (802.1AX).

FIG. 40 is a diagram showing the frame format for an Ethernet 2230 andPPP 2236 encapsulated Transparent Interconnection of Lots of Links(TRILL) frame. Although description and examples provided here willdescribe the Ethernet encapsulation 2230, those in the art will easilysee the implementation over PPP 2236 and other communications protocols.The Inner Ethernet Header 2233 and the Ethernet Payload 2234 come fromthe original frame and are encapsulated with a TRILL Header 2232 and anouter Ethernet header 2231 they travel between RBridges. Use of theTRILL header 2232 addresses many disadvantages of spanning tree andother forwarding methods by mitigating loops through the use of a hopcount field, eliminates the need for end station VLAN and MAC addresslearning in transit RBridges, directs unicast frames towards the egressRBridge which enables unicast forwarding tables of transit RBridges tobe sized with the number of RBridges rather than the total number of endnodes, and finally provides a separate VLAN tag for forwarding trafficbetween RBridges, independent of the VLAN of the native frame. Whenforwarding unicast frames between RBridges, the outer header 2231 hasthe MAC destination address of the next hop RBridge, to avoid frameduplication if the inter-RBridge link is multi-access. This also enablesmultipathing of unicast frames since the transmitting RBridge canspecify the next hop. Having the outer Ethernet header 2231 specify thetransmitting RBridge as the source address ensures that any bridgesinside the Ethernet cloud will not get confused, as they might be ifmultipathing is in use and they were to see the original source oringress RBridge in the outer header.

FIG. 41 shows a representative RBridge Port Model 2457 in more detail.The RBridge Port Model 2457 assumes connection to an IEEE 802.3 Link2464. An RBridge port can be modeled as having a lower level structuresimilar to that of an IEEE 802.1Q-2005 bridge port. An actual RBridgeport implementation may be structured in any way that provides thecorrect behavior. Low level control frames are handled in the lowerlevel port/link control logic 2462 in the same way as in an 802.1Q-2005bridge port. This may include but not be limited to a variety of 802.1or link specific protocols such as PAUSE (Annex 31B of 802.3), PFC(802.1Qbb, 802.3bd), link layer discovery (802.1AB), link aggregation(802.1AX), MAC security (802.1AE), or port based access control(802.1X). While handled at a low level, these frames may affect higherlevel processing. Higher-level control frames such as BPDUs and, ifsupported, VRP frames are not VLAN tagged and are handled by the RBridgeBPDU Processing 2460 and RBridge VRP Processing 2461 blocks. The upperinterface 2470 to the 802.1/802.3 Low Level Control Frame Processing,Port/Link Control Logic block 2462 corresponds to the Internal SublayerService (ISS) in IEEE 802.1Q. The upper interface 2469 to the802.1Q-2005 Port VLAN & Priority Processing block 2466 corresponds tothe Extended Internal Sublayer Service (EISS) in IEEE 802.1Q. The dottedlines indicate control only traffic 2474 a 2474 b 2474 c 2474 d. TheHigher Layer Entities 2467 may include but not be limited to theinter-port forwarding process, the IS-IS link state protocol, theRBridge manager.

FIG. 42 is a diagram of a TRILL RBridge with the addition of FIA Processand FIA Switch Client capability. The RBridge Model in FIG. 41 has beenmodified 2595 2500 to result in a FIA RBridge Port 2590, which combinesthe advantages of bridges and routers and is the application of linkstate routing to the VLAN-aware customer-bridging problem. Each RBridgeport 2592 can be coupled to one or more ENodes. The FIA Process deliversand accepts frames to and from the 802.1Q Port VLAN & PriorityProcessing block 3194, the RBridge Appointed Forwarder and InhibitionLogic 2584, the RBridge Relay Entity and Higher Layer Entities which mayinclude but be limited to the FIA Manager 3202, the System manager,IS-IS link state protocol. RBridge manager 2580. Further, FIG. 42 isonly one example of an implementation.

FIG. 43 is a diagram showing a FCoE frame 2620 sent from an Ethernetconnected ENode 2629 through a network of RBridge FIAs 2628 2627 2630 toa destination Ethernet connected ENode 2631 over a TRILL Ethernetnetwork 2626. FIA1 2628, FIA2 2627, and FIA3 2630 form an Ethernet TRILLnetwork 2626. The links from FIA1 2628 to ENode1 2629 and from FIA3 toENode2 2631 are Ethernet links 2652. The FCoE frame transmitted 2620from VN_Port1 2650 in ENode1 2629 includes the following values:Ethernet destination MAC address of the FIA Controller FCF_MAC address(FIACntlrMAC) 2625, Ethernet source MAC address of VN_Port1(VN_Port1MAC) 2650, a VID 2623, data 2622, and an FCS 2621. FIA1 2628substitutes the destination MAC address with VN_Port2 s MAC address(VN_Port2 MAC) 2615 and substitutes the source MAC address with the FIAController FCF-MAC address (FIACntlrMAC) 2614. After substituting thedestination Ethernet address 2615, FIA1 2628 encapsulates the frame in aTRILL frame. The outer destination Ethernet MAC 2619 address containsthe value of the next hop FIA MAC address, in this case the symbolic MACaddress FIA2MAC 2619. The outer source Ethernet MAC address 2618contains the value of the current FIA MAC address, in this case thesymbolic MAC address FIA1MAC. The frame is received by FIA2 2627 and theouter destination Ethernet MAC address 2641 is changed to be the nexthop, in this case FIA3 2630 and its symbolic Ethernet MAC addressFIA3MAC 2641. The outer source Ethernet MAC address 2640 is changed tobe FIA2s MAC address, in this case FIA2MAC 2640. The frame 2632 is thenreceived by FIA3 2630, the TRILL header is removed and transmitted toVN_Port2 2651 in ENode2 2631.

FIG. 44 is a diagram showing a Fibre Channel frame sent from a FibreChannel connected device through a network of FLAs to a destinationFibre Channel connected device. FIA1 2788, FIA2 2787, and FIA3 2789 forma TRILL Ethernet network. The links between FIA1 2788 and Fibre ChannelDevice1 2791 and between FIA3 2789 and Fibre Channel Device2 2792 areFibre Channel links. The Fibre Channel frame transmitted 2780 from FibreChannel Device1 2791 to FIA1 2788 contains Fibre Channel Device2's 2792address identifier 2710 of 02.02.02 as the destination addressidentifier 2784 and as the source address identifier 01.01.01 2783 thatof Fibre Channel Device1's 2791 N_Port1 ID 2709. FIA1 2788 encapsulatesthe frame 2780 in a FCoE header and a TRILL encapsulation over Ethernetframe 2779 2778 2777 2776. The resulting frame 2770 includes an innerdestination Ethernet MAC address 2775 that is the MAC address of givenby the FIA Controller to N_Port2 2710 in Fibre Channel Device2 2792.Note that this MAC address is only valid internally to the FIAs. Theinner source Ethernet MAC address 2774 is the Ethernet MAC address ofthe FIA Controller FCF-MAC address (FIACntlrMAC). The outer destinationEthernet MAC address 2779 is the Ethernet MAC address of FIA2 2787, theouter source Ethernet MAC address 2778 is the Ethernet MAC address ofFIA1 2788. The outer Ethernet addresses 2778 2779 follows the TRILLmethod of using RBridge hop to RBridge hop forwarding. When the frame isreceived from FLU 2787 it is forwarded to FIA3 2789 after the followingmodifications. The outer Ethernet destination MAC address 2702 ischanged to FIA3s 2789 MAC address, the outer Ethernet source MAC address2701 is changed to FIA2s 2787 MAC address. When the frame arrives atFIA3 2789, the TRILL frame is decapsulated into a FCoE frame 2703, whichis also decapsulated into the native Fibre Channel frame. The resultingFibre Channel frame is transmitted to N_Port2 2710 in Fibre ChannelDevice2 2792. Note for each hop through a TRILL network a new FCS iscalculated 2771 2794.

Shortest Path Bridging (SPB) is an IEEE draft (802.1aq) that may beincluded in the 802.1Q standard. There are two SPB models for multipathbridging: Shortest Path Bridging VLAN (SPBV) and Shortest Path BridgingMAC-in-MAC (SPBM). FIG. 45 is a diagram showing the interconnection ofENodes through a Shortest Path Bridging MAC-in-MAC (SPBM) network 2814.A FCoE frame 2820 sent from an Ethernet connected ENode 2818 through anetwork of FIA adapted to implement Shortest Path Bridging 2816 28152817 to a destination Ethernet connected ENode 2821 over a SPBM network2814. FIA1 2816, FIA2 2815, and FIA3 2817 form a SPBM 2814. The linksfrom FIA1 2816 to ENode1 2818 and from FIA3 2817 to ENode2 2821 areEthernet links 2820. The FCoE frame transmitted 2808 from VN_Port1 2819in ENode 1 2818 includes the following values: Ethernet destinationFCF-MAC address of the FIA Controller (FIACntlrMAC) 2813, Ethernetsource MAC address of VN_Port1 (VN_Port1MAC) 2812, a VID 2811, data2810, and an FCS 2809. FIA 1 2816 substitutes the destination MACaddress with VN_Port2 's MAC address (VN_Port2 MAC) 2805 and substitutesthe source MAC address with the FIA Controller FCF-MAC address(FIACntlrMAC) 2804. After substituting the destination Ethernet address2807, FIA1 2816 encapsulates the frame in a SPBM frame, i.e., adds aMAC-in-MAC header. The outer destination Ethernet MAC 2619 addresscontains the value of the egress FIA MAC address, in this case thesymbolic MAC address FIA3MAC 2817. The outer source Ethernet MAC address2806 contains the value of the current FIA MAC address, in this case thesymbolic MAC address FIA MAC. The frame is received by FIA2 2815 andforwarded to the egress FIA, FIA3 2817. FIA3 2817 removes the outer MACheader and forwards the frame to VN_Port2 2651 in ENode2 2631 with theinner source and destination Ethernet MAC addresses unchanged. TheShortest Path Bridging network in FIG. 44 can be adapted to use ShortestPath Bridging VLAN (SPBV) in lieu of SPBM by using the Shortest PathVLAN ID (SPVID) to designate nodal reachability.

FIG. 46 is a diagram showing a source and destination Ethernet MACaddress replacement logic. Certain fields from the incoming frame areloaded into received frame registers 3000. The fields include the sourceEthernet MAC address 3001, the Ethernet TYPE 3002, the Fibre Channeldestination address identifier (FC DID) 3003, and the destinationEthernet MAC address (Ethernet DA) 3005. The Ethernet TYPE field 3002 iscompared to 3011 the FCoE_TYPE 3010 value in the Ethernet TYPE Register3009. If the values are equal a Read EN signal 3012 is asserted and usedas a buffer enable to the data output 3007 of the FCID to MAC LookupTable 3004 and an input into the Source MAC Substitution FSM 3014. TheSource MAC Substitution FSM 3014 takes another signal, the entry_foundsignal from the MAC lookup table 3015 to select 3020 by a multiplexer3023 either the FIA Controller MAC 3013 or the received source EthernetMAC address for insertion into the source Ethernet MAC address in theoutgoing frame 3022. The FC DID field in the received frame is used asan address 3008 to lookup the assigned VN_Port MAC address 3006 in theFCID to MAC Lookup Table 3004. If an entry is found, the entry_foundsignal 3015 is asserted, and the VN_Port MAC buffer 3016 contains thematched VN_Port MAC address that corresponds to the Fibre Channeladdress identifier. The Destination MAC Substitution FSM 3019 selectswhich MAC address to use 3017, either the received Ethernet DA or thematched VN_Port MAC address, to insert into the Destination Ethernet MACaddress register 3018.

FIG. 47 is a diagram showing the migration of a Virtual Machine from aserver connected to a FIA to another server connected to another FIA.Virtual Machine 1 (VM1) 4004 in Server1 4005 is migrated 4008 to Server24007. Server1 4005 is connected to FIA1 4001. FIA1 4001 is connected tothe FIA Controller 4000. FIA1 is also connected to FIA2 4002. FIA2 4002is connected to FIA3 4003. FIA3 is connected to Server2 4007. The stepsinvolved in migrating VM1 4004 are further described. The hypervisorcontrol apparatus in Server1 4005 signals the FIA Controller 4000 of theimpending migration and that VM1 4004 has been temporarily suspended.Since both the MAC and Fibre Channel address identifier assignments forVN_Ports are centrally assigned and managed by the FIA Controller 4000,no address reassignment needs to be accomplished. After signaled by thehypervisor control apparatus in Server1 4005, the FIA Controller 4000sends messages to all FIAs 4001 4002 4003 to remove the MAC addressassigned to VM1 4005 from its forwarding tables. Clearing the forwardingtables cause the forwarding paths or routes to be recalculated. If theFIA is an Ethernet Bridge, the forwarding table is the FilteringDatabase, FIG. 10 403. The FIA Controller 4000 then responds to thehypervisor control apparatus that VM1 4004 migration 4008 to Server24007 is clear to proceed.

FIG. 48 is a diagram showing a distributed FIAC deployment. The diagramshows four FIACs, 4100 4101 4103 4104 and a central FIAC Datastore 4102.The FIAC Central Datastore 4102 is the central storage for certain RACinformation. The diagram also shows two core FIA's, FIA51 4105 and FIA524106, which interconnect all FIAC's 4100 4101 4103 4104, the FIACCentral Datastore 4102, and the forty FIA's which include FIA1 4107through 4026 FIA20 4108 and FIA21 4109 through 4027 FIA40 4110. Thereare also redundant connections 4019 between FIA51 4105 and FIA52 4106.Links 4020 4021 4022 4023 4024 4025 and 4019 may be Ethernet links. EachFIA connects a plurality of ENodes. For example, FIA1 4107 connects 4022to ENode1 4111 through ENode20 4112, ENode2 through ENode19 are notshown. FIA20 4108 connects 4023 to ENode1000 4113 through ENode10504114, ENode1001 through ENode1049 are not shown. FIA21 4109 connects4024 to ENode1051 4115 through ENode1100 4116, ENode1052 throughENode1099 are not shown. FIA40 4110 connects 4025 to ENode2000 4117through ENode2050 4118, ENode2001 through ENode2049 are not shown. TheFIAC's divide management of the FIAs. FIAC1 4100 manages FIA1 4107through FIA10 (not shown). FIAC2 4101 manages FIA11 (not shown) throughFIA20 4108. FIAC3 4103 manages FIA21 4109 through FIA30 (not shown).FIAC4 4104 manages FIA31 (not shown) through FIA40 4110. An FIAC managesa subset of FIA's, which allows a network to scale to a large number ofsupported ENodes by adding FIAC's. FIA management may include but not belimited to controlling the FIA FME and ACLE tables and responding to FIPand certain FCoE frames. For example, the FIA's forward FIP FLOGI framesto the FCF-MAC of the controlling FIAC. The FIAC's synchronize with eachother through the FIAC Central Datastore 4102. the FIAC CentralDatastore 4102 may be implemented by the following: a relationaldatabase, an object store database, in memory storage, and a filesystem.If the FIAC Central Datastore 4102 is implemented by a relationaldatabase then access to the database can support Structured QueryLanguage (SQL), which supports data insert, query, update, delete,schema creation and modification, and data access control.

Although the foregoing invention has been described in some detail byway of illustration and example for purposes of clarity andunderstanding, it may be readily apparent to those of ordinary skill inthe art in light of the teachings of this invention that certain changesand modifications may be made thereto without departing from the spiritor scope of the appended claims.

All publications and patents cited in this specification are hereinincorporated by reference as if each individual publication or patentwere specifically and individually indicated to be incorporated byreference in their entirety.

What is claimed is:
 1. A method for forwarding Fibre Channel overEthernet (FCoE) and FCoE Initialization Protocol (FIP) frames over aShortest Path Bridged network with a FCoE device interconnectionapparatus (FIA) under control of an FIA Controller, from a first FCoEdevice to a second FCoE device, the method comprising: receiving anincoming frame from the first FCoE device a first FIA and determining itthe frame is a FCoE frame or a FIP frame, if the frame is a FCoE frame:the frame including at least a destination address of a destinationEthernet Media Access Control (MAC) address of the HA controller and asource Ethernet MAC address, replacing the destination Ethernet MACaddress of the incoming FCoE frame with a destination Ethernet MACaddress of the second FCoE device as determined by a Fibre Channeldestination address identifier in the incoming FCoE frame, if the frameis a FIP frame, forwarding the frames with their destination and sourceEthernet MAC addresses of the FIP frame, and for both a FCoE frame and aFIP frame: replacing the source Ethernet MAC address of the incomingFCoE frame, encapsulating the frame in an outer MAC header, forwardingthe frame to an egress FIA, decapsulating at the egress HA the outer MACheader of the encapsulated frame into a decapsulated FCoE frame, andforwarding the decapsulated frame to the second FCoE device.
 2. Themethod of claim 1 wherein the source Ethernet MAC address of the saidincoming FCoE frame is replaced by a FCoE Forwarder Media Access Control(FCF-MAC) address of a FCoE device interconnection apparatus controller(FIAC).
 3. The method of claim 1 wherein when a FCoE InitializationProtocol (FIP) Fabric Login (FLOGI) request frame having originaldestination and Source Ethernet MAC addresses is received, the FIP FLOGIframe is forwarded to a FCoE device interconnection apparatus (FCIA)controller with the original destination and source Ethernet MACaddresses.
 4. The method of claim 1 wherein when a FCoE frame destinedto a Fabric Controller is received, the FCoE frame destined to theFabric Controller is forwarded with the original source and destinationEthernet MAC address.
 5. The method of claim 1 wherein when a MACencapsulated FCoE frame is received, the outer MAC header is removed,and the decapsulated FCoE frame is forwarded with the original sourceand destination Ethernet MAC addresses.
 6. The method of claim 1 whereinMAC encapsulated received FCoE frames are forwarded.